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
Copy file name to clipboardExpand all lines: .roo/rules/rules.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
- Before attempting completion, always make sure that any code changes have test coverage
6
6
- Ensure all tests pass before submitting changes
7
-
- The vitest framework is used for testing; the `describe`, `test`, `it`, etc functions are defined by default in `tsconfig.json` and therefore don't need to be imported
7
+
- The vitest framework is used for testing; the `vi`, `describe`, `test`, `it`, etc functions are defined by default in `tsconfig.json` and therefore don't need to be imported from `vitest`
8
8
- Tests must be run from the same directory as the `package.json` file that specifies `vitest` in `devDependencies`
9
9
- Run tests with: `npx vitest run <relative-path-from-workspace-root>`
10
10
- Do NOT run tests from project root - this causes "vitest: command not found" error
@@ -18,6 +18,7 @@
18
18
- Never disable any lint rules without explicit user approval
19
19
20
20
3. Styling Guidelines:
21
+
21
22
- Use Tailwind CSS classes instead of inline style objects for new markup
22
23
- VSCode CSS variables must be added to webview-ui/src/index.css before using them in Tailwind classes
0 commit comments