sourcegraph/client/branded
Felix Kling ebaab129ee
feat(svelte): Add support for creating search jobs from search results (#64308)
Closes srch-838

This commit extends the search progress popover and adds the search jobs
section.

In the React version the UI for the popover differs slightly when search
jobs are enabled vs not enabled.

I decided to ignore the differences and only impolemented the style used
for the 'search jobs enabled' version, which makes the popover a bit
more compact.

The logic for validating and creating a search job is encapsulated in a
class which makes it easy to conditionally show the search jobs UI.

Additional changes:

- Skipped items is now a list and uses `<details>` elements which is
semantically more correct. We loose the styling of the chevron but I
think that's OK.
- LoadingSpinner was updated to work inline.
- Logging was fixed (?) in the React version to send the correct
meta-data.
- Added integration tests for the search job popover behavior

## Test plan

Integration tests and manual testing.
2024-08-07 14:25:35 +02:00
..
src feat(svelte): Add support for creating search jobs from search results (#64308) 2024-08-07 14:25:35 +02: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.