artin/sourcegraph
1
0
Fork 0
mirror of https://github.com/sourcegraph/sourcegraph.git synced 2026-02-06 18:31:54 +00:00
Code Issues Packages Projects Releases Wiki Activity
wolfi-auto-update/main
sourcegraph/cmd/frontend
History
Felix Kling 34ff925ed8
feat(svelte): Add cody chat page (#64448) 
Closes #srch-906

This commit adds the cody chat page to svelte. This is simply reusing
the existing wrapper around the React component and renders it in a
standalone page.

When merged this will cause the cody chat page to be handled by new web
app on dotcom by default.

## Test plan

- Verified that chat loads and the tabs are clickable.
- Verified that the scroll behavior works as in the React app.
- Verified that the sidebar chat still works as expected (scroll
behavior, default context loading/switching)
2024-08-13 19:25:32 +00:00
..
auth chore: Move cmd/frontend/backend to internal (#64261) 2024-08-08 11:02:51 +02:00
dotcomproductsubscriptiontest feat/enterprise-portal: ConnectRPC layer for {Get/List}CodyGatewayAccess (#62771) 2024-05-27 13:39:57 -07:00
enterprise chore: Move cmd/frontend/webhooks to cmd/frontend/internal (#64157) 2024-08-05 16:46:38 +02:00
envvar Move dotcom check out of cmd/frontend (#60810) 2024-03-04 16:05:16 +00:00
graphqlbackend graphqlbackend: Move utils to internal/ (#64117) 2024-08-08 14:18:37 +02:00
hubspot chore: remove obsolete tracking code for Cody App downloads (#63364) 2024-06-23 21:48:31 -07:00
internal feat(svelte): Add cody chat page (#64448) 2024-08-13 19:25:32 +00:00
shared frontend: Consolidate remaining registry packages (#64156) 2024-08-05 16:29:50 +02:00
BUILD.bazel Revert "Revert "refactor: upgrade to rules_oci 2.0 (2nd attempt)"" (#64354) 2024-08-08 09:00:08 +00:00
image_test.yaml chore: Frontend does not need disk (#64273) 2024-08-06 13:22:00 +02:00
main.go feat(frontend): do not embed frontend assets anymore (#63946) 2024-07-31 15:17:52 +02:00
README.md

README.md

frontend

The frontend serves our web application and hosts our GraphQL API.

Typically there are multiple replicas running in production to scale with load.

Application data is stored in our PostgreSQL database.

Session data is stored in the Redis store, and non-persistent data is stored in the Redis cache.