You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under some cases, it will make the file's row length even longer.
I think it is sufficiently friendly for readability when we use writer with current indent setting.
What's more, it means that we should calculate the longest indent first in json object, and then insert some blank into other members to make name : value paris aligned on :.
Idea is not on changing names, but to add extra spaces between name closing quote and :. Within one object can be enough. We implemented it as writer builder option, harmless if not changed I believe.
I konw this idea is not on changing names, what I means is that adding extra spaces would make the file's row length even longer.
We already have indentations in every level, IMO, it is sufficiently friendly.
To use json files in a context where human readability makes sense, it's nice to have "name : value" pairs aligned on ":" at least within one object.
The text was updated successfully, but these errors were encountered: