Nice function for editing Json.
Would be great if it handled nesting (assuming it doesn’t I could not find a way to add nested things)
Play tool
JSON_Worker's itch.io pageResults
| Criteria | Rank | Score* | Raw Score |
| How much I could potentially use it in the future | #30 | 2.500 | 2.500 |
| Overall | #36 | 2.667 | 2.667 |
| How nice/fun it is to use | #39 | 2.750 | 2.750 |
| How original/innovative it is | #40 | 2.750 | 2.750 |
Ranked from 8 ratings. Score is adjusted from raw score by the median number of ratings per game in the jam.
Comments
Thanks!
As I know JSON-format (and as online JSON-validators can proof), this is valid behaviour; also test by Python 'json'-module, it can be correctly parsable.
I mean, that values, which you can type in app form, can be different types - not only integer numbers, for example.
But you right, there are big field to app impovement, and may be somewhen I upgrade it.
I think it is perfectly understandable to only support string types given the time constraints of the jam!
However, I feel it is a bit misleading to call the field (int/float/string/bool) when it only accepts strings. The behavior of compliant parsers will differ if they get a different data type (strongly typed languages might even refuse to parse into a struct that has the incorrect type!). For example JSON exported from your tool behaves strangely when parsed in my browser:
According to the JSON spec (https://www.crockford.com/mckeeman.html) there is a difference between a string containing an integer (‘”’ characters ‘”’ e.g. "123") and an integer (onenine digits e.g. 123).
I understand the confusion, as formal language grammar is complicated, and the many formats used don’t help at all. So I don’t think this is a serious deficiency in your tool, just maybe something to consider in the future 😉 I hope this did not come across as too negative, I rewrote this message several times to make it sound less unfriendly 😢. I just wanted to show that in JSON these things matter!
1 year ago(+1)
Thanks!
I do some additional test and understood, that you and Léon was right and plain types dont need to be 'strings' in result.
(...really, it can be - but only if after parse you convert fields by-hand, and this is terrible practice...)
Online validators fake me. =((
I update the tool when I can.
Sorry for unfunctional tool. =(
1 year ago(+1)
Now tool correctly save type of boolean and number values and for work with js JSON.parse() method you can also click 'Export as string', with this option in JSON-file to data added `` (`...data...`)...so in values must not contain symbol '`'.
Thanks for advises.
I like the colorful UI and buttons. There was clearly an attempt made to make everything follow certain design rules (e.g. “clear” = orange).
The key/value pairs here could use more work. For example you could split them into lines or bullet points, and make the labels bold or otherwise different.
See https://design.mindsphere.io/patterns/key-value.html
Edit: I just realized the “export strict” feature doesn’t generate valid JSON:
name=PLAIN=NONE%
tags=OBJECT=COMMA%
Leave a comment
Log in with itch.io to leave a comment.