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
JSON5 introduces some really nice quality of life improvements for JSON files, including trailing commas (yes!) and the ability to have comments (yaaaaaasssss!). We should change the mbed-tools python package (would probably need to make a fork) to parse JSON files (mbed_app.json, mbed_lib.json, targets.json) with a json5 parser.
The text was updated successfully, but these errors were encountered:
yaml translates perfectly to json, and it's not only humane readable, it's also humane writable.
not all things need to be rewritten in yaml, but new things could use it and convert to json for processing (if not used directly which is almost the default anywhere now).
That could be pretty sweet too. The only issue I could think of is that if we converted targets.json to YAML, it would make it a pain to merge changes from upstream that modify the json version.
JSON5 introduces some really nice quality of life improvements for JSON files, including trailing commas (yes!) and the ability to have comments (yaaaaaasssss!). We should change the mbed-tools python package (would probably need to make a fork) to parse JSON files (mbed_app.json, mbed_lib.json, targets.json) with a json5 parser.
The text was updated successfully, but these errors were encountered: