silberengel
/
gc-alexandria
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Browse Source

Update Svelte component rules

master
buttercat1791 10 months ago
parent
f4d9874983
commit
e1b3ec95e1
1 changed files with 2 additions and 0 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      .cursor/rules/svelte-style.mdc

2
.cursor/rules/svelte-style.mdc
Unescape View File

@ -21,6 +21,8 @@ Observe the the following style guidelines when programming Svelte components or
- Avoid trying to trigger reactivity by reassigning state variables unless other options have failed. - Avoid trying to trigger reactivity by reassigning state variables unless other options have failed.
- Write components in TypeScript, and prefer strong typing for variables, props, and function signatures. - Write components in TypeScript, and prefer strong typing for variables, props, and function signatures.
- Limit component logic to rendering concerns. Extract business logic into separate TypeScript modules, and import functions and classes into Svelte components as needed. - Limit component logic to rendering concerns. Extract business logic into separate TypeScript modules, and import functions and classes into Svelte components as needed.
- Use PascalCase when naming Svelte components.
- Keep component files under 500 lines, when possible.
## Component Code Organization Example ## Component Code Organization Example

Write Preview
Loading…
Cancel
Save