This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Look for more opportunities to use x:UId #4711
michael-hawker
started this conversation in
Ideas
Replies: 3 comments
|
Hello michael-hawker, thank you for opening an issue with us! I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌 |
0 replies
|
@RosarioPulella this could be a good thing to keep an eye on while you're reviewing any other PRs and ramping on the project. Feel free to comment and make suggestions for anything on this Issue, thanks! |
0 replies
|
@michael-hawker Sounds good, I'll keep an eye out. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We should investigate where we can use/add more x:UId to components for more flexible customization of components/text (or if we've missed any in our resources).
We should also have a test which checks overriding these from the app level as can be done with
GetLocalizedin #3460 and as verified by @vgromfeld here.Originally posted by @michael-hawker in #3460 (comment)
All reactions