-
Notifications
You must be signed in to change notification settings - Fork 28
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
Repair mixed close-brackets: using } instead of ] or the other way around #88
Labels
enhancement
New feature or request
Comments
Good idea! so, basically repair an array that ends with |
Thinking about it: the library already repairs missing closing brackets, so to address this, we should probably only remove redundant close brackets (which in itself is also good: repairing |
Great! The redundant bracket thing was meant to by my second example but I
think I wrote it incorrectly but glad it made sense regardless :)
…On Fri, Feb 17, 2023 at 3:22 AM Jos de Jong ***@***.***> wrote:
Good idea! so, basically repair an array that ends with } instead of ],
and repair an object that ends with ] instead of }.
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUCBE2SEXDWF4TNXHWYWQGDWX4YKRANCNFSM6AAAAAAU64TYRM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This is supported now, fixed by implementing #103 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello! Was hoping you could support JSON errors that looks like this:
{"topics": ["Hallstead Jewelers", "Lake Avenue and Second Avenue", "Washington Street", "Tiffany &" }}
or
{"topics": ["Hallstead Jewelers", "Lake Avenue and Second Avenue", "Washington Street", "Tiffany &" }]
The text was updated successfully, but these errors were encountered: