sourcegraph/client/branded
Felix Kling 82372119fe
fix(svelte): Prefill search home page query input with (default) context filter (#63740)
Closes srch-103

Currently we don't show the global context filter on the search home
page or the search results page (global context is the default context).

This commit does two things:

- It prefills the search input on the search homepage with the user's
default context (like the React app)
- It the logic that pre-processed the search query and removed the
context filter if it was global.

In other words we simplify the query logic by showing/submitting the
search query as is. Notably this doesn't affect how the search input
works on repo pages.


## Test plan

- Opening the search home page pre-fills the query input with the
default search context
- Submitting a query without a `context:` filter does not add a
`context:` filter to the URL or the search input
- If a query contains `context:global` that filter is preserved in the
query input (it wasn't before)
2024-07-09 22:02:04 +00:00
..
src fix(svelte): Prefill search home page query input with (default) context filter (#63740) 2024-07-09 22:02:04 +00:00
.bazelignore web: drop legacy GraphQL schema generator (#45945) 2022-12-25 18:10:20 -08:00
.stylelintrc.json web: integrate @sourcegraph/stylelint-plugin-sourcegraph and ban bootstrap imports (#34956) 2022-05-05 04:27:26 +00:00
BUILD.bazel Search: remove keyword toggle (#63584) 2024-07-03 10:53:33 -07:00
package.json reapply "switch from jest to vitest for faster, simpler tests (#57886)" (#58145) 2023-11-07 12:00:18 +02:00
README.md web: drop bootstrap depenedency (#41401) 2022-09-07 03:11:26 -07:00
tsconfig.json reapply "switch from jest to vitest for faster, simpler tests (#57886)" (#58145) 2023-11-07 12:00:18 +02:00
vitest.config.ts reapply "switch from jest to vitest for faster, simpler tests (#57886)" (#58145) 2023-11-07 12:00:18 +02:00

Branded

This folder contains client code that is branded, i.e. it implements the visual design language we use across our web app and e.g. in the options menu of the browser extension. Code here can use global classes and must not adapt styles of the code host (for more details, see Styling UI in the handbook).

Any code that is code host agnostic should go into ../shared instead.