fix: handle multiple nested condition objects in exports field#36
Open
WilliamTomOBrien wants to merge 2 commits intolukeed:masterfrom
Open
fix: handle multiple nested condition objects in exports field#36WilliamTomOBrien wants to merge 2 commits intolukeed:masterfrom
WilliamTomOBrien wants to merge 2 commits intolukeed:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #35
In the case where there are multiple condition objects in the exports field, where the first has a top level condition that is true, but does not contain any object paths with all true conditions, but latter condition objects do have a correct resolution, these changes should allow for a correct resolution.