Default context is always set to the user and potentially breaks all existing search URLs
Created by: rvantonder
It can be a nice thing to set the default context to the current user, but this also breaks existing search URLs. I believe this behavior is a breaking change. For example, if I previously linked a query somewhere (embedded in a website, like our search docs, saved it in a note, whatever) like:
Then search contexts will automatically apply me as the user, and if I don't have the gorilla/mux repo in my context, then it breaks and there are no results (I have to set search to global, whereas previously it worked before). Problematically, if I set search to global, the webapp doesn't preserve this setting, so I have to do this each time for the linked URL).
I am not necessarily proposing that we default to to global (although if we don't, then the above is going to potentially break for any existing search query URLs saved somewhere or embedded in a website). I would propose that the app at least remembers that I set global if there is no context specified, because otherwise I have to set this each time. If we remember the previous setting in the absence of a context, then the breaking change will only require users to meddle with this once per saved URL, and not for every previously saved URL.