Opened 11 years ago
Closed 11 years ago
#12751 closed bug (fixed)
parseJson error throwing doesn't match JSON.parse behavior
| Reported by: | hustonjs | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | unfiled | Version: | git |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Currently when you call parseJson on , "", or {} you get null back. If you call JSON.parse on the same values it throws an error. After lots of conversation at the summit majority seemed to lean towards making the functionality of the 2 match.
Note: See
TracTickets for help on using
tickets.
Fix #12751. Ensure parseJson throws in the same situations as JSON.parse. Close gh-993.