Repository navigation
Conversation
expandOrTerm only appended isLicense() terms, so a LicenseRef alternative of OR was dropped before Satisfies ran. expandAndTerm already kept LicenseRef nodes; mirror that in expandOrTerm. Fixes github#165.
Collaborator
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
expandOrTermonly keptisLicense()leaves when flattening an OR. ALicenseRef-*alternative was dropped beforeSatisfiesran, so:Satisfies("MIT OR LicenseRef-x", []string{"LicenseRef-x"})returnedfalseSatisfies("MIT AND (LicenseRef-a OR LicenseRef-b)", []string{"MIT"})returnedtrue(the required refs vanished)expandAndTermalready kept LicenseRef nodes; this mirrors that inexpandOrTerm.Fixes #165.
Test plan
go test ./... -count=1TestSatisfiesLicenseRefORandTestExpandOrKeepsLicenseRefcover the failing shapes from Satisfies ignores a LicenseRef alternative of an OR #165