[BUG] Bad unicode in object description

[iann0036]

API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/36de5cef6b87d3122e7b2eef3db30da49ef0f88f/specification/security/resource-manager/Microsoft.Security/preview/2023-12-01-preview/automations.json

API Spec version

2023-12-01-preview

Describe the bug

At

azure-rest-api-specs/specification/security/resource-manager/Microsoft.Security/preview/2023-12-01-preview/automations.json

Line 615 in 36de5ce

"description": "The Log Analytics Workspace to which event data will be exported. Security alerts data will reside in the 'SecurityAlert' table and the assessments data will reside in the 'SecurityRecommendation' table (under the 'Security'/'SecurityCenterFree' solutions). Note that in order to view the data in the workspace, the Security Center Log Analytics free/standard solution needs to be enabled on that workspace. To learn more about Microsoft Defender for Cloud continuous export capabilities, visit https://aka.ms/ASCExportLearnMore",

, the characters at the beginning of the description field which look like spaces are bad unicode equivalents. They broke some personal automation.

Expected behavior

The description should be free of irregular unicode points.

Actual behavior

The description field begins: The�Log�Analytics�Workspace�to�which�event

Reproduction Steps

See file.

Environment

No response

[zzhxiaofeng]

@Nessya123 Please help have a look, thank you.

[Nessya123]

@zzhxiaofeng - how can I push a fix to the repo?

[raych1]

@Nessya123 , can you create a PR with the changes to the repo?

[Nessya123]

@raych1 - should I fork the repo and then create a PR? sorry, I am not familiar with the process.

[raych1]

@Nessya123 , yes, please. I thought you updated the swagger last time, didn't it?

[Nessya123]

Hi,

I opened a PR with a fix that already approved with all required approvals, and it's pending merge:
#28984

[Nessya123]

The PR with the fix is merged.

[Nessya123]

Bug is resolved