-
-
Notifications
You must be signed in to change notification settings - Fork 237
feat: add onBundle
callback
#391
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
base: main
Are you sure you want to change the base?
Conversation
This functionality mimics the @jonluca, could you please advise what the test should be? |
Head branch was pushed to by a user without write access
Hello, The logic looks sound, I think you just need to fix the test comparison. The bundle traversal is stable, right? The tests aren't failing based on platform, so just make sure yarn test returns 100% on your local machine. |
Manual execution has shown that correct I'm wary of saying that this is a bug in the @jonluca, could you please clarify whether this behavior of |
}, | ||
{ | ||
path: "#/definitions/a", | ||
value: { $ref: "#/definitions/apath: "#/definitions/b", |
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.
this is missing a comma and closing quote
That is not the issue, the issue is that there is a syntax error in your code. https://github.com/APIDevTools/json-schema-ref-parser/pull/391/files#r2181747158 The original error is that your deep expect is incorrect. https://github.com/APIDevTools/json-schema-ref-parser/actions/runs/16018336530/job/45189942210 If you fix the hardcoded object it should pass. Please run the tests locally before submitting an update and verify they all succeed. |
Head branch was pushed to by a user without write access
Apologies, I didn't push the test I was debugging. |
Awesome, can you remove the console log? Otherwise looks good |
Removed. |
There it is: a failed test. |
Can you change the test to just Modifying the refs is how the internal bundler works, it's up to the caller of the |
This PR adds functionality, as well as an options object, for the
bundle
method, which consists of:onBundle
callback.excludedPathMatcher
callback.Closes #346