Allow unknown identifiers #85
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jake-Shadle
force-pushed
the
allow-unknown
branch
from
48163b1 to
dc4d668
Compare
Contributor
|
Thank you so much, Jake! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Allows parsing of unknown license or exception identifiers if
ParseMode::allow_unknownis true. Rather than complicating the API, allowing unknown identifiers will assume the intent of the user based on the identifier position, if it follows aWITH|withit's assumed to be an exception, and is treated as anAdditionRef-that the user forgot to clarify. If the identifier is in the position that would be valid for an SPDX short id, it is treated as aLicense-Refin a similar manner.Resolves: #82