fix(nlab-api): support Controller paths and imported DTOs - #109
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Controller generation stopped at ordinary path templates such as
/detail/{taskId}and local string constants. Support these mappings in the Controller adapter, carry required path parameters through the shared OpenAPI and TypeScript pipeline, and match concrete paths in Mock rules.Resolve DTOs imported through
package.*before falling back to globally unique names, while preserving ambiguity and explicit qualified-name boundaries. Include the existing main worktree's Codex and JTH configuration changes.Validation: