Handle non wellformed JSON for request bodies

[MIchaelMainer]

Describe the bug
Request bodies with trailing JSON commas cause Graph Explorer to perform in an unexpected way. JSON spec does not allow trailing commas.

To Reproduce
Steps to reproduce the behavior:

1. Go to Graph Explorer
2. Sign in.
3. Create a POST or PATCH request with a request body that contains a trailing comma.
4. See error in console.

Expected behavior
We show an error message stating that the supplied JSON is invalid.

Screenshots

**Desktop **

• Browser chrome, edge

Additional context
Incident 187938447

[JimmyLS]

Based on my testing, the issue occurred if request syntax error (like invalid JSON) detected in PATCH/POST method, or even send an empty request body.
No error indicated user to correct request syntax, the query just stuck or hang there without any response until you refresh browser.
This is quite confusing and annoying experience to users.

[JimmyLS]

Hi Guys,

Just want to check when we can fix this bug?

Thanks.

[JimmyLS]

Hi Team,

It's still not working on my side. The symptom is the same.

[ddyett]

this change hasn't deployed yet. Current schedule is later this week.

[JimmyLS]

this change hasn't deployed yet. Current schedule is later this week.

Thanks! I will try this next Monday.

[JimmyLS]

Hi Team,

May I know if the change has been deployed now? I tried it today but looks like still didn't work.

Thanks.

[JimmyLS]

Sorry, I test in the local instance and it worked, version 4.1.3.

May I know then this version can be published to the public instance?

[MIchaelMainer]

@JimmyLS We are awaiting a resolution to a related deployment blocker.

[JimmyLS]

Thank you so much!