Do not use hashes for SPDX license names/expressions #3844
Merged
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.
This PR takes the recent full text license work and updates how we're interpreting the
value
field when converting to spdx. Given that we no longer worry aboutfullText
being included in this field,value
is now treated like Expressions when calculating the ID for SPDX licenses in the format helpers.This means longer
value
that exceeded 64 characters in length do not lose information when being set to the SPDX license ID. We previously becausevalue
was a dump for both full text and anything NOT valid spdx expressions.Type of change
Checklist: