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.
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.
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
build: allow auto-discover all typings files in npm package by ts-api-guardian #35691
build: allow auto-discover all typings files in npm package by ts-api-guardian #35691
Changes from all commits
3884c40
e3e5524
0f9c30c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this is a symptom from an issue where the golden file does not yet exist, so
require.resolve
(runfile resolution) won't work? I think we should respect this environment variable in theresolveBazelFilePath
variable if the runfile resolution fails. What do you think?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BUILD_WORKSPACE_DIRECTORY
will only be available duringbazel run
, so it only really comes into play for us when we are attempting to generate and write the file.During a
bazel test
this environment variable is not available, so we would have to fallback anyway in this case inside of theresolveBazelFilePath
function.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense. Optional: Add a comment for this here, and maybe also add a comment in
resolveBazelFilePath
that the try/catch is needed for resolution of files within tree artifacts?You might able to just make this a noop-catch and
return fileName;
should do the same. I think we neededpath.relative
only for the absolute resolved path from the manifest.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added in the comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding these! Could we make those more concrete/helpful by saying that:
In
resolveBazelFilePath
: We need thetry/catch
to handle file resolution for tree artifacts where individual files inside the tree artifact (e.g.npm_package
) are not declared outputs and cannot be resolved through the manifest?The BUILD_WORKSPACE_DIRECTORY variable is needed only for approving the golden in case the golden is not existing and the golden file is not symlinked/part of the manifest. Right?