Add support for LazyItemScope scoped modifiers #221
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.
The
ComposeContextnow tracks an additional variable,scope, which users can use inComposeVieworComposeModifierViewto access scoped modifiers. https://developer.android.com/develop/ui/compose/modifiers#scope-safetyI've also added a new variant of
.composeModifier(scope:)that allows users to declare a class to which their(Modifier) -> Modifierfunction will be scoped, making it easy to access modifiers scoped to that class.Finally, I've set the
scopevariable inLazyHStack,LazyVStack,LazyHGrid, andLazyVGrid. There are probably a lot more places where this could be set.Thank you for contributing to the Skip project! Please use this space to describe your change and add any labels (bug, enhancement, documentation, etc.) to help categorize your contribution.
Skip Pull Request Checklist:
swift test