#36: Two SkeletonForEach in a LazyVGrid causes duplicate IDs#56
Open
Viktor-by wants to merge 1 commit intoCSolanaM:developfrom
Open
#36: Two SkeletonForEach in a LazyVGrid causes duplicate IDs#56Viktor-by wants to merge 1 commit intoCSolanaM:developfrom
Viktor-by wants to merge 1 commit intoCSolanaM:developfrom
Conversation
Two SkeletonForEach in a LazyVGrid causes duplicate IDs
Viktor-by
changed the title
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.
Issue Link 🔗
#36
Goals ⚽
Enabled
LazyVGridto contain multipleSkeletonForEachwith loading stateImplementation Details 🚧
idfor a skeleton view inSkeletonForEachto make sure there is no 2 or more skeleton views with the sameidTesting Details 🔍
No new tests added