You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- First, check whether a similar proposal has already been made
64
-
- If not, [create an issue](https://github.com/continuedev/continue/issues)
65
-
- Please describe the enhancement in as much detail as you can, and why it would be useful
64
+
- First, check whether a similar proposal has already been made
65
+
- If not, [create an issue](https://github.com/continuedev/continue/issues)
66
+
- Please describe the enhancement in as much detail as you can, and why it would be useful
66
67
67
68
- Join the [Continue Discord](https://discord.gg/NWtdYexhMs) and tell us about your idea in the `#feedback` channel
68
69
@@ -140,12 +141,12 @@ nvm use
140
141
141
142
2. Start debugging:
142
143
143
-
1. Switch to Run and Debug view
144
-
2. Select `Launch extension` from drop down
145
-
3. Hit play button
146
-
4. This will start the extension in debug mode and open a new VS Code window with it installed
147
-
1. The new VS Code window with the extension is referred to as the _Host VS Code_
148
-
2. The window you started debugging from is referred to as the _Main VS Code_
144
+
1. Switch to Run and Debug view
145
+
2. Select `Launch extension` from drop down
146
+
3. Hit play button
147
+
4. This will start the extension in debug mode and open a new VS Code window with it installed
148
+
1. The new VS Code window with the extension is referred to as the _Host VS Code_
149
+
2. The window you started debugging from is referred to as the _Main VS Code_
149
150
150
151
3. To package the extension, run `npm run package` in the `extensions/vscode` directory, select `Tasks: Run Task` and
151
152
then select `vscode-extension:package`. This will generate `extensions/vscode/build/continue-{VERSION}.vsix`, which
@@ -192,6 +193,22 @@ To keep the Continue codebase clean and maintainable, we expect the following fr
192
193
Continue uses [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) to format
193
194
JavaScript/TypeScript. Please install the Prettier extension in VS Code and enable "Format on Save" in your settings.
194
195
196
+
### Theme Colors
197
+
198
+
Continue has a set of named theme colors that we map to extension colors and tailwind classes, which can be found in [gui/src/styles/theme.ts](gui/src/styles/theme.ts)
199
+
200
+
Guidelines for using theme colors:
201
+
202
+
- Use Tailwind colors whenever possible. If developing in VS Code, download the [Tailwind CSS Intellisense extension](https://marketplace.visualstudio.com/items?itemName=bradlc.vscode-tailwindcss) for great suggestions
203
+
- Avoid using any explicit classes and CSS variables outside the theme (e.g. `text-yellow-400`)
204
+
205
+
Guidelines for adding/updating theme colors:
206
+
207
+
- Choose sensible VS Code variables to add/update in [gui/src/styles/theme.ts](gui/src/styles/theme.ts) (see [here](https://code.visualstudio.com/api/references/theme-color) and [here](https://www.notion.so/1fa1d55165f78097b551e3bc296fcf76?pvs=25) for inspiration)
208
+
- Choose sensible Jetbrains named colors to add/update in `GetTheme.kt` (flagship LLMs can give you good suggestions to try)
209
+
- Update `tailwind.config.js` if needed
210
+
- Use the Theme Test Page to check colors. This can be accessed by going to `Settings` -> `Help` -> `Theme Test Page` in dev/debug mode.
211
+
195
212
### Testing
196
213
197
214
We have a mix of unit, functional, and e2e test suites, with a primary focus on functional testing. These tests run on
@@ -239,10 +256,10 @@ model:
239
256
240
257
-[AddNewModel page](./gui/src/pages/AddNewModel/configs/) - This directory defines which model options are shown in the
241
258
side bar model selection UI. To add a new model:
242
-
1. Add a `ModelPackage` entry for the model into [configs/models.ts](./gui/src/pages/AddNewModel/configs/models.ts),
243
-
following the lead of the many examples near the top of the file
244
-
2. Add the model within its provider's array
245
-
to [configs/providers.ts](./gui/src/pages/AddNewModel/configs/providers.ts) (add provider if needed)
259
+
1. Add a `ModelPackage` entry for the model into [configs/models.ts](./gui/src/pages/AddNewModel/configs/models.ts),
260
+
following the lead of the many examples near the top of the file
261
+
2. Add the model within its provider's array
262
+
to [configs/providers.ts](./gui/src/pages/AddNewModel/configs/providers.ts) (add provider if needed)
246
263
- LLM Providers: Since many providers use their own custom strings to identify models, you'll have to add the
247
264
translation from Continue's model name (the one you added to `index.d.ts`) and the model string for each of these
0 commit comments