-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Use real root filename as theoretical root yaml file #322
Conversation
…name of the root spec (often openapi.yaml). This fixes issues with resolving references in rules such as unsused-components.
e3e9a67
to
bc413a1
Compare
…en the spec's root does not exist on the filesystem (either read from remote URL or []byte)
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #322 +/- ##
=======================================
Coverage 99.63% 99.63%
=======================================
Files 164 164
Lines 16586 16627 +41
=======================================
+ Hits 16526 16567 +41
Misses 55 55
Partials 5 5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
a6c319d
to
e4a49c0
Compare
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 will break some elements of the library, I will make a list of them.
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.
LGTM
Instead of using "root.yaml" as a theoretical root, use the real filename of the root spec (often openapi.yaml). This fixes issues with resolving references in rules such as unused-components.