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
Doesn't correctly parse numbers immediately before a brace. #10
Comments
Thank you for the report. Should be fixed in the latest commit. I tested it with your file. Let me know whether or not it works for you. |
I commented on the commit, but I'll comment here, too. It's working fine now with the latest commit. I glanced at the code and was considering trying to fix it myself, but you certainly beat me to it. |
You're brave. I wrote this library with no regard for maintainability or even comprehensibility. |
Hah -- I've been an engineer since 1988 -- so have seen much uglier code
than yours. I'm sure that I could have figured it out -- eventually. :)
…On Tue, Feb 2, 2021 at 9:44 AM StringEpsilon ***@***.***> wrote:
You're brave. I wrote this library with no regard for maintainability or
even comprehensibility.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEIYQZFFNRGSZ3H2PPF4VTLS5A2XFANCNFSM4W6ZQMKQ>
.
--
------------------------------------------------
Rick Hale (rickh57@gmail.com)
|
I'm using the covid-193.p.rapidapi.com. It returns JSON like this:
After parsing with JsonItem and dumping, I see this:
Numbers directly followed by
,
, such as"recovered":10448406,
are parsed OK. However,"total":154522}
isn't parsed -- with an empty string being captured.The text was updated successfully, but these errors were encountered: