Modifier.sentryTag uses Modifier.Node #4029
Open
+80
−6
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.
📜 Description
Converts
Modifier.sentryTag
to be implemented withModifier.Node
.fixes #4028
💡 Motivation and Context
Currently,
Modifier.sentryTag
prevents composable skipping, due to creating a lambda within a non-@Composable
function.Assuming the
@Composable
annotation cannot be added (might be a breaking change if other developers have usedModifier.sentryTag
outside of a@Composable
context), then aModifier.Node
implementation will help avoid recomposition.💚 How did you test it?
I did build a UI test for this, but was unsure how to run it.
📝 Checklist
sendDefaultPII
is enabled.🔮 Next steps