feat(nestjs-trpc): Support for nesting Router within custom applyDecorators implementations #51
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Someone is attempting to deploy a commit to the Kevin's Projects Team on Vercel. A member of the Team first needs to authorize it. |
mrosnerr
commented
Dec 8, 2024
| if (options.autoSchemaFile != null) { | ||
| const fileScanner = new FileScanner(); | ||
| const callerFilePath = fileScanner.getCallerFilePath(); | ||
| const rootModuleFilePath = callerFilePath[0]; |
There was a problem hiding this comment.
[note] It seemed to make sense to just leave this usage as the root file
…rators implementations
mrosnerr
force-pushed
the
support-nesting-router-via-applyDecorators
branch
from
b0cdffa to
e884039
Compare
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.
Summary
Fixes #50
The changes here:
FileScanner.getCallerFilePath()to return an array which now contains a broader list of potentially important files by pulling more from the call stack.findClassInPathwhich can be used to search thepatharray for the class highest up in the call stack.findClassInPathwith the newpatharray to find the class to use.