WIP: Code conventions for new code matching existing style#2043
WIP: Code conventions for new code matching existing style#2043misha-db wants to merge 3 commits into
Conversation
|
🤖 Integration tests triggered for |
|
🤖 Integration tests ✅ all 35 test jobs passed for |
rugpanov
left a comment
rugpanov
left a comment
There was a problem hiding this comment.
Solid, accurate onboarding doc — the suffix taxonomy, DI, event/disposal idioms, vscode-objs/ seam, decorators, and test suffixes all match the codebase. A few additions from a recent structural audit that fill gaps here, all consistent with the "match the current setup" framing (no new abstractions):
rugpanov
left a comment
rugpanov
left a comment
There was a problem hiding this comment.
Two more, focused on navigation (finding where a feature lives / where to add code):
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
|
🤖 Integration tests triggered for |
2 participants
Changes
Describes existing code style and naming conventions. So new code can follow the same principles
Tests
Manually