RichCommands: Open settings

[ferrariofilippo]

Resolved / Related Issues

• Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
  Closes Generalizing Rich Command Usage #11481

I'd like to add a shortcut. Which one is better: Ctrl + S, Alt + S or anything else?

Validation
How did you test these changes?

• Did you build the app and test your changes?
• Did you check for accessibility? You can use Accessibility Insights for this.
• Did you remove any strings from the en-us resource file?
  • Did you search the solution to see if the string is still being used?
• Did you implement any design changes to an existing feature?
  • Was this change approved?
• Are there any other steps that were used to validate these changes?
  1. Open settings

[yaira2]

ctrl + ,

[Jay-o-Way]

General question: why do you guys never use x:UID to fetch strings?
https://learn.microsoft.com/dotnet/desktop/xaml-services/xuid-directive

[ferrariofilippo]

General question: why do you guys never use x:UID to fetch strings?

Honestly, I've never heard of it. Isnt' it only supported by UWP and WPF?

[yaira2]

Binding to the strings allows us to have more control, it's also more readable since you can tell which properties are being translated at a glance.

[yaira2]

LGTM

Can you add this to the documentation?

[yaira2]

Please don't use the closes tag for these PRs 😃

[ferrariofilippo]

Please don't use the closes tag for these PRs 😃

I'm sorry I always forget to change that

[ferrariofilippo]

Can you add this to the documentation?

Yeah sure