-
-
Notifications
You must be signed in to change notification settings - Fork 248
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
fix(ruleset-migrator): resolve npm packages correctly #2022
Conversation
59d873d
to
9468469
Compare
65ae608
to
5deeba8
Compare
expect(isPackageImport(input)).toBe(true); | ||
}); | ||
|
||
it.each(['', '/nimma/legacy', 'path', 'https://cdn.skypack.dev/@stoplight/spectral-core'])( |
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 it worth also adding spectral:oas
as an example here?
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.
could add it, though in reality isPackageImport
is unlikely to ever receive stoplight:oas
as it's being replaced with @stoplight/spectral-rulesets
here https://github.com/stoplightio/spectral/blob/develop/packages/ruleset-migrator/src/transformers/extends.ts#L21
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
# [@stoplight/spectral-ruleset-migrator-v1.7.2](https://github.com/stoplightio/spectral/compare/@stoplight/spectral-ruleset-migrator-v1.7.1...@stoplight/spectral-ruleset-migrator-v1.7.2) (2022-01-26) ### Bug Fixes * **ruleset-migrator:** resolve npm packages correctly ([#2022](#2022)) ([843e47c](843e47c))
🎉 This PR is included in version @stoplight/spectral-ruleset-migrator-v1.7.2 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
As noted in stoplightio#2022, the version pinning can only be done using `package.json`s, not the `extends` rule.
As noted in stoplightio#2022, the version pinning can only be done using `package.json`s, not the `extends` rule.
As noted in stoplightio#2022, the version pinning can only be done using `package.json`s, not the `extends` rule.
As noted in stoplightio#2022, the version pinning can only be done using `package.json`s, not the `extends` rule.
Fixes #2019
Checklist
Does this PR introduce a breaking change?