[NT-2010] Add capability for nested personalization#106
Merged
Alex Freas (akfreas) merged 1 commit intoJan 8, 2026
Merged
Conversation
Alex Freas (akfreas)
requested review from
Maroun (maroun9t),
Maximilian Rauh (maxrawlinger) and
Charles Hudson (phobetron)
as code owners
Alex Freas (akfreas)
force-pushed
the
NT-2010-nested-personalizations-react-native-squashed
branch
from
10022d1 to
5f01a50
Compare
Charles Hudson (phobetron)
approved these changes
Jan 8, 2026
Collaborator
Charles Hudson (phobetron)
left a comment
Charles Hudson (phobetron)
left a comment
There was a problem hiding this comment.
✨ 🌟 ⭐
Alex Freas (akfreas)
deleted the
NT-2010-nested-personalizations-react-native-squashed
branch
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
2 participants
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.
Allow personalizations to be nested in the component and add e2e tests.
Creating a new PR with the hope that it solves the consistently failing e2e test issue - nothing was changed in the test infrastructure and the e2e tests are passing on
main.