feat: experimental support for splitting code by tags / route segments #134
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
introduces a new experimental option
--grouping-strategy
used by thetypescript-koa
template to split the routes into separate files, based on either their first
tag
or route segment.includes a lot of refactoring to support this:
ImportBuilder
now supports relative paths in different directoriesTypeBuilder
/SchemaBuilder
now gets anImportBuilder
scoped to the collection of routes being built for a given output fileJoiSchemaBuilder
and fixed a few bugs in the processlint-staged
command foreslint
there's still quite a bit of impedance mismatch that makes outputting in different ways like this more
challenging than it would ideally be, mainly that we go straight from
IRModel
->string
and quicklyloose context of that string (eg: what imports it depends on, where it is used)
eventually we'll probably need to introduce some wrapping object, similar to the
CompilationUnit
introduced in this change that can track interesting things and allow us to be smarter about how
we organize the resulting files.