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
According to the documentation around Parse, it is recommended to invoke @valid to ensure that your json is in a correct format if you are uncertain. Given the following test case with a BOM, we can see the expected behavior occuring. In this case, a byte string with a BOM validates as false; which is intended.
I have discovered an issue where requesting a JSON data return that includes a file BOM header will result in parsing failure
The text was updated successfully, but these errors were encountered: