Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This introduces a mbstring library requirement. So it may not be a good merge candidate but wanted to detail the issue. (utf8_decode may also handle it and am not sure if it introduces the mbstring requirement)
A little more in-depth on what is going on in my use case.
We use MaxMind's geoip to add server variables for country/city/etc. Sao Paulo has an accent over the a (ala São Paulo). Not sure if MaxMind is the issue or what but thousands of errors are showing up in Raygun due to our uptime monitor being located in São Paulo and everytime it tries to json_encode it throws up with "invalid UTF-8 sequence".
This is what MaxMind GeoIP shows: S\xe3o Paulo.
Let's discuss how we can handle this so these false positive errors go away and I can clean up my Raygun dash. Another alternative may be to allow me to ignore those variables the same way that you could white/blacklist per my other feature request #32.
Thanks!