You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have Verify tests which compares the swagger files and notifies us if something has changed per accident.
Now we have the issue because of the addition of #2899 that this produces different results, locally (Windows) and on our Azure Pipelines (Linux). The comparison fails!
The easiest fix would be to make this optionally configurable and let the user decide.
This way I could then fixate the newline characters
Would be a very nice addition.
Thank u!
Greetings
Florian
Expected behavior
Newline Characters are configureable
Actual behavior
Newline Characters are defined by Environment.Newline which differs from the Operating System
Steps to reproduce
No response
Exception(s) (if any)
No response
Swashbuckle.AspNetCore version
6.6.2
.NET Version
net8.0
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Personally I'd push back on this being a bug per-se, as using Environment.NewLine is a common thing to do, but I can see why this would be annoying in your use case.
We can look at seeing if we can make this configurable in future, but for now I would suggest adjusting your verification tests to ignore line endings.
Tip:
For anyone stumbling on this, don't forget that you need to replace the string \r\n not the control characters.
This way you replace the characters in the json string (in my case) ^^
Describe the bug
We have Verify tests which compares the swagger files and notifies us if something has changed per accident.
Now we have the issue because of the addition of #2899 that this produces different results, locally (Windows) and on our Azure Pipelines (Linux). The comparison fails!
The easiest fix would be to make this optionally configurable and let the user decide.
This way I could then fixate the newline characters
Would be a very nice addition.
Thank u!
Greetings
Florian
Expected behavior
Newline Characters are configureable
Actual behavior
Newline Characters are defined by Environment.Newline which differs from the Operating System
Steps to reproduce
No response
Exception(s) (if any)
No response
Swashbuckle.AspNetCore version
6.6.2
.NET Version
net8.0
Anything else?
No response
The text was updated successfully, but these errors were encountered: