sourcegraph/client/shared
Naman Kumar d0b88533b4
Remove old Cody Web completely (#64345)
closes:
https://linear.app/sourcegraph/issue/SRCH-622/remove-old-cody-web-entirely

Removes the old Cody Web completely.

## Test plan

- sg start
- visit /cody/chat and you should see the new unified panel Cody Web
without having to turn on any feature flags.
- check the blob view sidebar for the same.
## Changelog

- The new Cody Web is enabled by default and the older version of Cody
Web is completely removed from both standalone chat and sidebar.
2024-08-09 10:25:59 +05:30
..
dev chore(ci): remove Percy visual tests (#63515) 2024-06-27 16:20:06 +02:00
src Remove old Cody Web completely (#64345) 2024-08-09 10:25:59 +05:30
.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 chore(svelte): Cleanup dependencies (#63691) 2024-07-08 17:54:44 +02:00
NOTICE Move all client code into client/ folder (#14480) 2020-10-07 22:23:53 +02:00
package.json feat/dotcom: use Enterprise Portal for Cody Gateway usage (#63653) 2024-07-10 19:22:08 +00: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.