-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Prioritized] Normalize line endings #2453
Comments
Doing some digging into this. Found this issue which is basically exactly our scenario. So I think we need to create a custom We should also update our we load the recording to ignore |
I think the issue is with the actual content, not the formatted JSON. When matching we renormalize the JSON anyways so it should handle this for us. But the issue happens when someone adds line breaks based on Environment.NewLine from their own test into the request content. The workaround is to either hard-code the new line value or just remove them. |
Yeah I'm seeing this now.
Hmmm. So add a hardcoded replace on
I can see how this might be the proxy's place to do this, but I'm super leery towards it. Bright side is that this is not a breaking change. Existing recordings would just have |
Agreed that this shouldn't be a breaking change. I think essentially normalizing the line breaks when matching is the way to go. |
@JoshLove-msft @scbedd
The text was updated successfully, but these errors were encountered: