You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO UNLICENSED should be recognised as not needing a URL.
IMO the lint could also stipulate that UNLICENSED means the identifier field (SPDX) must not be present, as they are mutually exclusive.
Describe alternatives you've considered
Disabling the lint locally is a workaround, but then if someone adds a URL, and it is malformed, the linter will ignore it. Or someone helpfully but incorrectly adds "identifer: Unlicense" that should be blocked by the linter.
Additional context
The text was updated successfully, but these errors were encountered:
I think this does not comply to the OpenAPI specification. To cover your case, you can either suppress that particular warning with the ignore file or write your rule via a custom plugin.
Oh, sorry, I didn't mean it's against the spec. I was trying to say that that particular case is not described anywhere in the OpenAPI. So for me it doesn't make sense to modify our existing rule.
Is your feature request related to a problem? Please describe.
For an private API, we are using
This is used to match the license value recommended in npm docs: https://docs.npmjs.com/cli/v10/configuring-npm/package-json
redocly lint emits warning
Describe the solution you'd like
IMO UNLICENSED should be recognised as not needing a URL.
IMO the lint could also stipulate that UNLICENSED means the
identifier
field (SPDX) must not be present, as they are mutually exclusive.Describe alternatives you've considered
Disabling the lint locally is a workaround, but then if someone adds a URL, and it is malformed, the linter will ignore it. Or someone helpfully but incorrectly adds "identifer: Unlicense" that should be blocked by the linter.
Additional context
The text was updated successfully, but these errors were encountered: