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

Migration from INI to YAML #43

Open
hatkidchan opened this issue Jun 27, 2023 · 1 comment
Open

Migration from INI to YAML #43

hatkidchan opened this issue Jun 27, 2023 · 1 comment

Comments

@hatkidchan
Copy link
Owner

Using INI as configuration format adds a lot of headaches. The only reason post_init exists on filters is because we can't load all filters immediately. Using YAML would solve pretty much all of the configuration problems, as well as may allow for multiple sources to be used simultaneously within one file. Plus, it makes usage of filters and integrations more explicit.

The only downside I see is that we can no longer use same filter in multiple output modules, as well as we can't use variables from one module in another. That, however, can be solved by creation of shared filters and variables.

The other option is to fucking fix current configuration loader which should've been done a while ago.

@CyberTailor
Copy link
Contributor

YAML is the most complicated file format in the universe. Seems like overkill.

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