This is autogenerated. Please review and update as needed.
Describe the bug
Command Nameaz repos pr list Extension Name: azure-devops. Version: 0.25.0.
Errors:
If the Pull request's Title or Description (and possibly other elements) contain non-ascii characters (in this case unicode 0x96) , these are outputted 'as-is', instead of being properly serialized into two bytes.
Because of that the file fails to conform to standard, and is therefore invalid.
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
Put any pre-requisite steps here...
Enter a Pull request with title containing long dash "–"(character 0x96).
az repos pr list --organization {} --project {} --repository {} --status {} > file.json
execute the above from cmd.exe, not powershell.
Expected Behavior
The produced json file should encode the 0x96 character in UTF8 as two bytes: 0xC2 0x96 .
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az repos pr list Extension Name: azure-devops. Version: 0.25.0.Errors:
If the Pull request's Title or Description (and possibly other elements) contain non-ascii characters (in this case unicode 0x96) , these are outputted 'as-is', instead of being properly serialized into two bytes. Because of that the file fails to conform to standard, and is therefore invalid.
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
Put any pre-requisite steps here... Enter a Pull request with title containing long dash "–"(character 0x96).
az repos pr list --organization {} --project {} --repository {} --status {} > file.jsonexecute the above from cmd.exe, not powershell.Expected Behavior
The produced json file should encode the 0x96 character in UTF8 as two bytes: 0xC2 0x96 .
Environment Summary
Additional Context