Fix missing spdx license expression in license detection #4023
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.
Context
Occassionally, the spdx license expression is missing in license detections even though the license expression itself is non-null and a matching spdx expression would be available.
Should fix #4015
Summary
In the post processing step clues are converted to detections under certain conditions. This entails that their license expression may be updated if it was previously
None
. In these cases, we also need to update the spdx license expression.It seems that this fix covers at least some instances of the bug, that I know of.
Test Plan
Run scancode on the example from #4015
The result:
scancode_null_expression.json
Tasks
Run tests locally to check for errors.