Just small remarks for using "real" JSON with Leo:
*Background:*
Some applications have settings or data stored in "fake" json files, which
support line-comments (with "//"). This is an addition to the json
standard, for commodity. Its not part of the official JSON standard.
More serious software handle only real json files, without possibility of
comments. Clever webdevs have been using json entries with a "//" as the
key to comment parts of their json. But it can get ugly with decorators as
no duplicates are allowed in non-array objects. etc.
*User case: *
Big json files, like the one that manages almost all aspects of a vscode
extension, would gain a lot by being viewed as a structure, because the
files get very long.
In fact its quite rare that xml or json files are so small that they fit in
the screen and the structure is visually apparent at a glance. such as
this:
*"container": {*
* "child1":"content1",*
* "child2": {*
* "grandChild1": 1234,*
* "grandChild2": 5678,*
* }*
*}*
Its more like files with thousands of lines, and so, bracket pair color
match, and other little helpers do not suffice to understand the structure
without long minutes of exploring the long linear scroll of indented text.
*Solution*
So here comes Leo: Structure the json like a boss in an @clean node, with
clear and obvious sections, organized to illustrate meaning or intent.
*And to top it off, @clean won't break the json with comment decorators! *
So, in conclusion, Leo's pretty cool.
--
Félix
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/8385e97e-8745-4a68-b2d5-c0b92622e7e4o%40googlegroups.com.
