-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider format of version control log fille #4546
Comments
JSON would be easy to implement and is quite human readable. One potential disadvantage compared to Cylc (modified INI) format is readability of the Cylc format (note the whitespace is important for the meaning, the status letters are in specific columns):
JSON (possibility): {
"status": [
" M flow.cylc",
"A whatever.txt"
]
} Having said that, it's not looking bad |
It's overkill for our purposes now, but we could always do
|
I don't think we can do that - it loses the columns
As long as each status line is recorded, no need to process them any further |
Actually, if I can turn it to JSON in half an hour, it might be worth doing now? Would probably save effort in the long run |
Up to you - Don't forget that you need to update the rose interface to match |
in metomi/rose#2510 there is a brief discussion about the most appropriate way to store version control information. It seems sensible to store it in either JSON, XML (parsers available in the standard library) or the Cylc data format to make reading it easier for other programs.
Pull requests welcome!
The text was updated successfully, but these errors were encountered: