31
down vote
accepted
Both forms are valid. However, for an API, I would recommend the second form. The reason is that it gives you a path for expansion of your API.
For example, if you have an API getUsersInGroup which returns an array of user objects, and later you decide you want to include, say, some aggregate statistics about the users being returned, there's no easy way to do that without breaking existing clients (or including lots of redundant data in each user object). If you use an object, you simply add another field to the object which is silently ignored by clients on a previous version of the API.
In short, try to avoid top-level primitives wherever possible in your API, and you'll find it easier to expand in the future.
pour manipuler du json en cmdline à la jq
Kinto is a lightweight JSON storage service with synchronisation and sharing abilities.
ça peut servir
Bash scripting will never die!
How to pretty print a json string :
cat pref.json | python -m json.tool
for uuoc nazi ;) :
< pref.json python -m json.tool
or
python -m json.tool < pref.json
Pour rendre un json lisible :
cmd_qui_donne_du_json | python -mjson.tool