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
I originally reported this issue here: hpi-swa/Squot#316 (The .ston file is not relevant in this context, of course). It would be great if the JSON files could be formatted a bit more consistently, i.e. closing brace with the same indentation a spacing as the relevant opening brace etc.
The text was updated successfully, but these errors were encountered:
I've got mixed emotions about changing file formats in "midstream". I tend to agree that the format can be improved, but when a release is made with a change in format, all projects end up with massive format only changes intermixed with semantic changes ... and even worse if multiple developers are contributing to the same project and one of them has not updated to the new format, you not only end up with massive changes, but then you have to deal with massive commit conflicts the majority of which are cosmetic ...
tonel has exactly the same problem ...
My plans for Rowan involves including a format type in one of the properties files that will make it possible for Rowan (at least) to adapt to a variety of tonel (and filetree) "canonical" file formats on a project by project basis and minimize the format churn introduced by by the different filetree and tonel formats that exist in the wild ...
I originally reported this issue here: hpi-swa/Squot#316 (The
.ston
file is not relevant in this context, of course). It would be great if the JSON files could be formatted a bit more consistently, i.e. closing brace with the same indentation a spacing as the relevant opening brace etc.The text was updated successfully, but these errors were encountered: