{"action":"opened","issue":{"url":"https://api.github.com/repos/MicrosoftDocs/feedback/issues/585","repository_url":"https://api.github.com/repos/MicrosoftDocs/feedback","labels_url":"https://api.github.com/repos/MicrosoftDocs/feedback/issues/585/labels{/name}","comments_url":"https://api.github.com/repos/MicrosoftDocs/feedback/issues/585/comments","events_url":"https://api.github.com/repos/MicrosoftDocs/feedback/issues/585/events","html_url":"https://github.com/MicrosoftDocs/feedback/issues/585","id":348131489,"node_id":"MDU6SXNzdWUzNDgxMzE0ODk=","number":585,"title":"Obvious method to add a scope to a search query","user":{"login":"sparkchaser","id":1392511,"node_id":"MDQ6VXNlcjEzOTI1MTE=","avatar_url":"https://avatars0.githubusercontent.com/u/1392511?v=4","gravatar_id":"","url":"https://api.github.com/users/sparkchaser","html_url":"https://github.com/sparkchaser","followers_url":"https://api.github.com/users/sparkchaser/followers","following_url":"https://api.github.com/users/sparkchaser/following{/other_user}","gists_url":"https://api.github.com/users/sparkchaser/gists{/gist_id}","starred_url":"https://api.github.com/users/sparkchaser/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sparkchaser/subscriptions","organizations_url":"https://api.github.com/users/sparkchaser/orgs","repos_url":"https://api.github.com/users/sparkchaser/repos","events_url":"https://api.github.com/users/sparkchaser/events{/privacy}","received_events_url":"https://api.github.com/users/sparkchaser/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-08-07T01:12:46Z","updated_at":"2018-08-07T01:12:46Z","closed_at":null,"author_association":"NONE","body":"Example scenario: I want to look up API documentation for, say, `Enumerable.FirstOrDefault()`.  I start off at docs.microsoft.com.  I use the search box at the top of the page and search for \"FirstOrDefault\", yielding 397 search results.  Limiting my search to just .NET would likely give better results, so I have to do the following:\r\n\r\n1. Click the \"Docs\" link at the top to return to the docs.microsoft.com main page.\r\n2. Dig through the list at the bottom to find the scope I'm looking for, then click on it.\r\n3. Re-enter my search terms on this page and search again.\r\n\r\nNow, I have just 55 results, and the results are significantly more relevant.\r\n\r\nThe problem is, adding this search scope required several steps and navigating multiple additional pages.  I had to somehow already know that search scopes were a thing that existed, plus where to find a page that included a pre-scoped search field.  _Removing_ a search scope modifier is just one simple click, though.\r\n\r\nThis feature is horribly asymmetrical.  Adding a search scope should be as simple as removing one.  If there's an existing way to add a search scope from the search field or from the search results page, it needs to be made discoverable.\r\n\r\nI tried including the scope in the query, like `.NET FirstOrDefault`.  That generated an unscoped search yielding 29,619 results.  Enclosing the desired scope in braces or brackets (like a StackOverflow tag) didn't help, nor did trying to format it like a search engine keyword (`scope:.NET`), a DuckDuckGo-style bang operator (`!.NET FirstOrDefault`), a command line flag (`/scope .NET`, `--scope=.NET`), a SQL query (`where scope = .NET`), or a natural language query (`FirstOrDefault in .NET`).  The only way to add a scope without jumping through hoops appears to be to manually hack a `&scope=` parameter to the end of the URL, but that's error-prone and a horrible user experience."}}
{"actor":{"display_login":"sparkchaser"}}