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

Use yaml configuration files instead of current custom specification #17

Open
heuristicus opened this issue Feb 5, 2021 · 1 comment

Comments

@heuristicus
Copy link

The custom specification could probably be replicated in yaml without issue and would mean that the sheriff_config file would no longer be necessary. Perhaps there isn't much to be gained from this, but a custom parser and file format is not ideal.

@mcamurri
Copy link

mcamurri commented Feb 9, 2021

I agree that would be nice, but since the internal parser works fine I would keep it that way.

Migrating to yaml would have the only benefit for new users, who do not have to learn a custom syntax for a config file. It is something we might want to consider in the future, but not now.

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