-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Additional config formats #164
Milestone
Comments
Cannot agree more! |
chfw
added a commit
that referenced
this issue
Jan 22, 2019
…oaded and used by moban. what's more, 'overrides' syntax is promoted to accept any data format, child.yml could override parent.json. related to #164
With the new implementation, a new feature emerges: any data file can override any data file. for example: child.yaml:
or child.json:
|
and new data loader can be added in the same way as jinja2 plugins. |
Merged
all other data config could be written as a built-in module if no external dependencies or as a moban plugin. Hence, case closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently moban only supports yaml as the config format.
anytemplate uses anyconfig to support:
It would probably make sense to define a plugin layer for input data formats, keep the existing yaml as a native plugin, and add a 'anyconfig' plugin which provides supports for all the other formats.
I can see a lot of potential for growth by adding specific file formats, like .spec , and more complex data structures like SPDX license metadata files (so that templates do not need to load large data files).
The text was updated successfully, but these errors were encountered: