-
-
Notifications
You must be signed in to change notification settings - Fork 247
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
JSON extension: v2.6 #1212
base: master
Are you sure you want to change the base?
JSON extension: v2.6 #1212
Conversation
This is perfect! |
I have a new update which includes more blocks. |
can add export and import lists? |
Sure |
@GarboMuffin can you please check if its okay |
another 6 months passed |
😭 |
@GarboMuffin merge this already 😭😭😭 |
THEN HOW COME ANOTHER VERSION OF THIS EXTENSION WAS MERGED THAT ONLY ADDED THE FIX VALID VALUE THING BUT NOT THIS ONE 😭 |
Yelling at volunteers is not going to merge things faster, this repo is notoriously very slow at merging extensions |
i know i know i know... |
We will celebrate the first anniversary of this pull in a month |
Please update the pr and fix merge conflicts, cause otherwise this is perfectly fine (at first glance), ill do a more indepth check when its mergable |
This comment was marked as abuse.
This comment was marked as abuse.
@yuri-kiss I think the conflicts are resolved. can you please check again? |
} | ||
json = json.trim(); | ||
if ( | ||
(json.slice(0, 1) != "[" || json.slice(-1) != "]") && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why cant you just do json[0] or json.at(0) and json.at(-1), is there any benifit?, this isnt a review bc im just curious lol
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did it pop up like a review :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a conflict from #1596
So I copied the code from there
Perhaps I can change it after this
🤷
misc change
{"key":123}
are considered valid json now (leading & trailing spaces)blocks added