sourcegraph/client/shared
Julie Tibshirani 2afbe46b39
Revert "web: navigate to file@commit instead of file@branch" (#62889)
This reverts commit e45c2ed.

We've decided to revert this behavior after receiving negative feedback from
several customers. Instead, we'll work to improve indexing speed and
reliability to minimize drift between search results and the file view.
2024-05-24 08:59:07 -07:00
..
dev bazel: refactor percy mocha tests to js_test instead of js_run_binary + build_test (#60983) 2024-03-26 10:58:20 +00:00
src Revert "web: navigate to file@commit instead of file@branch" (#62889) 2024-05-24 08:59:07 -07:00
.bazelignore bazel: remove schema.ts entries (#48976) 2023-03-08 20:25:29 -08:00
.eslintignore bazel: remove schema.ts entries (#48976) 2023-03-08 20:25:29 -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 Svelte: Add basic telemetry to svelte implementation (#62190) 2024-04-26 12:56:33 +02:00
NOTICE Move all client code into client/ folder (#14480) 2020-10-07 22:23:53 +02:00
package.json Svelte: Add basic telemetry to svelte implementation (#62190) 2024-04-26 12:56:33 +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

Shared

This folder contains common TypeScript/React/SCSS client code shared between the browser extension and the web app.

Everything in this folder is code-host agnostic and cannot make assumptions about whether it is running inside the Sourcegraph web app, in the browser extension on GitHub, Gitlab, Phabricator, Bitbucket Server, etc. In particular, components cannot make use of global CSS classes but must accept CSS classes as props and/or have their own code host agnostic SCSS stylesheets. For more details, see Styling UI in the handbook.

Code that is only used in branded contexts (web app, options menu of the browser extension, ...) should go into ../branded instead.