change UserStateScheme property in XCUserData from Array into Set #757
Conversation
This file contains 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
|
Thanks @JCSooHwanCho - looks like we both submitted fixes 😅 We'll likely need to keep the existing array to maintain the current public API without introducing breaking changes. I think this PR could be a good candidate for the next major release. |
|
Replaced by #756 |
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.
Resolves #756
Short description 📝
Although
UserStateSchemeinXCUserDatahas dictionary representation actually, It was converted as Array. This bug is blocking bumping up dependency version in Tuist.related PR: here
Solution 📦
make that property as Set
Implementation 👩💻👨💻