Adding url encoding wrapper function to handle xaml textbox conversio…

[jlevier]

…n of new line to only carriage return

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• New feature or enhancement
• UI change (please include screenshot!)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Internationalization and localization
• Other (please describe):

What is the current behavior?

Issue Number: #758

What is the new behavior?

• Due to TextBox.AcceptsReturn lost \n in UWP microsoft/microsoft-ui-xaml#1826, it seems that the xaml textbox is converting a new line to a single carriage return. This resulted in the url encoding not properly handling the user input. This change will support if the decision is made to convert to carriage return + line feed or just line feeds.

Other information

Quality check

Before creating this PR:

• Did you follow the code style guideline as described in CONTRIBUTING.md
• Did you build the app and test your changes?
• Did you check for accessibility? On Windows, you can use Accessibility Insights for this.
• Did you verify that the change work in Release build configuration
• Did you verify that all unit tests pass
• If necessary and if possible, did you verify your changes on:
  • Windows
  • macOS (DevToys 2.0)
  • Linux (DevToys 2.0)

[veler]

Hi @jlevier ,

Thanks for this pull request. It looks great!

As a heads-up, it may be fixed in DevToys 2.0 in a different manner as we plan to use Monaco Editor for every multiline editors. But we didn't try it yet for this particular scenario. Anyway, we will make sure to keep this new unit test and adapt it when we port this tool to dev/2.0 branch.

[jlevier]

Ok, sounds great. Thank you so much for the speedy review!