We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The CLI will error when trying to use a migration template file that doesn't exist. An example of the current error message:
$ squill new --template missing --name this Error: failed to render template: Template 'missing/new.up.sql' not found
This message comes almost directly from Tera. A better error message would include Squill-specific information:
templates_dir
A sketch of something better:
Error: failed to render template: `.squill/templates/missing` not found
Error: failed to render template: `.squill/templates/missing/up.sql` not found
Error: failed to render template: `.squill/templates` (templates_dir) not found
Error: failed to render template: no templates_dir configured
It may be easier to track which template files exist by tracking them in a map explicitly instead of using the one big tera::Tera instance.
tera::Tera
Multi-template support was added in #168
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The CLI will error when trying to use a migration template file that doesn't exist. An example of the current error message:
This message comes almost directly from Tera. A better error message would include Squill-specific information:
templates_dir
) doesn't existtemplates_dir
is unconfigured/defaultA sketch of something better:
Implementation notes
It may be easier to track which template files exist by tracking them in a map explicitly instead of using the one big
tera::Tera
instance.Multi-template support was added in #168
The text was updated successfully, but these errors were encountered: