[BUG] Publisher adding characters when API specification contains ° or ³
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Description
### Release version
APIOps Toolkit for Azure APIM v5.1.4
### Describe the bug
When publishing an API specification that contains ° or ³, the final result of our schema definitions contains `°C` instead of `°C` and `³` instead of `³`.
Our specification.yaml file contains the following lines:
components:
schemas:
Conditions:
type: object
properties:
temperature:
type: number
description: Temperature (°C)
gasContent:
type: number
description: Content of gas (mg/Nm³)
description: Conditions
which results in a definition in APIM with schema:
{
"type": "object",
"properties": {
"temperature": {
"type": "number",
"description": "Temperature (°C)"
},
"gasContent": {
"type": "number",
"description": "Content of gas (mg/Nm³)"
}
},
"description": "Conditions"
}
### Expected behavior
When providing a specification that contains `°` or `³`, the schema published in API Management contains `°` and `³` without any additional characters.
### Actual behavior
When providing a specification that contains `°` or `³`, the schema published in API Management contains `°` and `³`.
### Reproduction Steps
Publish an API specification with a schema that contains a special character such as `°` or `3`.
Contributor guide
Assessment
This issue has not been assessed yet.