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

Making cosmo optional and questioning the "standalone" version #84

Open
Omikhleia opened this issue Dec 9, 2024 · 0 comments
Open

Making cosmo optional and questioning the "standalone" version #84

Omikhleia opened this issue Dec 9, 2024 · 0 comments

Comments

@Omikhleia
Copy link
Contributor

Omikhleia commented Dec 9, 2024

This module includes a reader, several writers, a command-line converter, and a standalone converter (which vendors C code and some libraries, including cosmo).

This packaging does not seem ideal.
Notably the cosmo dependency is only used in the latter case, if I am not mistaken -- and for sure, not in the reader.
All components however depend on the same util.lua that always require cosmo.

In use cases where one only needs the reader (implementing their own writers/renderers) or doesn't need the templating engine anyway, this forces having cosmo installed.
There should be a way to make it more modular.

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

1 participant