You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was curious if you would find any benefit to use a config file in addition to args for minijinja-cli.
My use-case is I always want these args set --env --trim-blocks --lstrip-blocks --autoescape=none but having them be read from a config file instead would be awesome to I don't need to continue putting them in the CLI command.
So instead of running minijinja-cli --env --trim-blocks --lstrip-blocks --autoescape=none ... I could do the below:
Purposed CLI
minijinja-cli --config minininja.toml ...
Note: --config could be defaulted to minininja.toml if found so it could be even simpler by just running minijinja-cli ...
Hi 👋🏼
I was curious if you would find any benefit to use a config file in addition to args for minijinja-cli.
My use-case is I always want these args set
--env --trim-blocks --lstrip-blocks --autoescape=none
but having them be read from a config file instead would be awesome to I don't need to continue putting them in the CLI command.So instead of running
minijinja-cli --env --trim-blocks --lstrip-blocks --autoescape=none ...
I could do the below:Purposed CLI
minijinja-cli --config minininja.toml ...
Note:
--config
could be defaulted tominininja.toml
if found so it could be even simpler by just runningminijinja-cli ...
Purposed Config file
Thanks for this very useful tool!
The text was updated successfully, but these errors were encountered: