Skip to content
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

Switch config file format? Or allow multiple? #32

Open
relleums opened this issue Oct 17, 2017 · 3 comments
Open

Switch config file format? Or allow multiple? #32

relleums opened this issue Oct 17, 2017 · 3 comments

Comments

@relleums
Copy link
Member

relleums commented Oct 17, 2017

This should not surprise anybody. It lead for me to an error which we did not understand at first.
I copied the config text from the webbrowser and pasted it into an empty text file. This caused white space/tab confusions and the last line of the seperator.yaml was not parsed and not applied. On behalf of Max I create this issue to keep the incident in mind.
Maybe a different config file based on sth. white space insensitive like JSON or XML 🔥 would be a solution.

@maxnoe
Copy link
Member

maxnoe commented Oct 17, 2017

I want to keep yaml. Indentation is nice, but should be checked carefully.

I wanted to have this issue to have better error reporting in case things go south.
E.g. Not all needed features were found in the input data. Missing keys are: ['area', ]. Check your model and your config file.

@maxnoe
Copy link
Member

maxnoe commented Jan 22, 2020

Seems like TOML is nowadays a good alternative for config files,
much less confusing and powerfull (a good thing imho) than yaml while not having the shortcomings of json (readability, no comments, no inf / nan)

@maxnoe
Copy link
Member

maxnoe commented Jan 22, 2020

@maxnoe maxnoe changed the title yaml config files are sensitive to whitespace mayhem Switch config file format? Or allow multiple? Jan 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants