Skip to content

test: add tsArch to check for module-structure #83

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
emaarco merged 1 commit into from
Oct 21, 2026
Merged

test: add tsArch to check for module-structure #83

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,7 @@ them on a private corpus without copying it into the repository, are described i
without changing it is a view (`query/`); deciding positions is `layout/`, or `format/` when a
user asks for it; geometry more than one engine needs is `diagram/`; text or JSON for the user
is `report/`; anything that touches the file system or `process` is `node/` or `cli.ts`.
`test/architecture.test.ts` keeps the root of `src/` to the three entries.
- `test/`: the vitest suite. It also pins the documentation: the README quick start and the
examples in `docs/` must match what the CLI prints. `test/setup.ts` clears `BPMN_KEEP_FLOW_IDS`
of your shell before every file, so the tests see the CLI's defaults.
Expand Down
Loading
Loading