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: .github/copilot-instructions.md
+28-2Lines changed: 28 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,8 +12,34 @@
12
12
- Maintain consistency in terminology throughout the codebase
13
13
- Prefer "folder" to "directory"
14
14
15
-
## Code Style
15
+
## TypeScript Code Style
16
16
17
-
- Follow the existing ESlint TypeScript conventions in this project (`typescript-eslint`rules)
17
+
- Follow the existing ESlint TypeScript conventions (the rules defined by the `typescript-eslint`and `prettier` projects)
18
18
- Use consistent formatting and naming conventions based on prettier and ESLint configurations
19
19
20
+
## Documentation
21
+
22
+
- Add comprehensive TSDoc comments accepted by API Extractor
23
+
- Document all classes, methods, properties, parameters, and return types
24
+
- Document private and protected members as well
25
+
- Keep the line length below 80 characters
26
+
- If the code already includes documentation, review and possibly improve it
27
+
- Preserve the `// eslint-disable-next-line` comments when present
28
+
- Use `@remarks` for additional detailed notes or explanations within TSDoc comments; this should be placed after the summary and before any tags
29
+
- Use `@param` and `@returns` tags appropriately in TSDoc comments; place `@param` tags immediately after the summary and before `@returns`
30
+
- Use `@throws {@link ExceptionName}` for exceptions and place the descriptions on the next line; place these tags after `@returns`
31
+
- Precede `@throws` tags with an empty line, and place the description on the next line
32
+
- Do not documnent exceptions thrown by assertions
33
+
- Do not add `@public` or `@internal` tags
34
+
- When generating lists in TSDoc `@remarks` comments, use html `<ol>` and `<li>` tags for ordered lists, and `<ul>` and `<li>` tags for unordered lists.
35
+
- inside html lists, do not use markdown syntax for bold or italics, use `<b>`, `<i>` html tags instead
36
+
- inside html lists, do not use markdown syntax for code, use `<code>` html tags instead
37
+
- inside html lists, do not use `{@link name}` syntax for links, use `<code>` html tags instead
38
+
- outside of html lists, use markdown syntax for code (`code`) and links (`{@link name}`)
39
+
- In the `@remarks` section, first explain why the method or property is useful, then explain how to use it, and finally provide any additional notes or details.
40
+
41
+
## Folder Structure
42
+
43
+
-`/src`: Contains the TypeScript source code
44
+
-`/tests`: Contains the test suites and test cases
45
+
-`/templates`: Contains any template files used for code generation or project scaffolding
0 commit comments