Daniel Imms
5b4b93acc6
- Enhanced copilot instructions with detailed architecture overview - Added comprehensive development workflow documentation - Documented addon development patterns and key examples - Added project-specific conventions and TypeScript structure - Included common patterns for parser integration and buffer access - Added critical implementation details for rendering and events - Created unit test instructions file with addon testing rules - Specified preferences for assertions and self-documenting tests
331 B
331 B
applyTo
| applyTo |
|---|
| **/*.test.ts |
When writing unit tests follow these rules:
- When writing unit tests for addons, always create a real xterm.js instance instead of mocking it.
- Prefer
assert.okoverassert.notStrictEqualwhen checking something is undefined or not. - Avoid comments as most tests should be self-documenting.