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
.yml
When defining template context files (the YAML) files, these are only recognised when they use the full .yaml extension.
.yaml
When using the shorter .yml extension the template is not picking up the context file.
This can be very confusing.
django-patter-library
test.html
django-pattern-library
{{ test_var }}
test.yaml
context: test_var: Test content
mv test.yaml test.yml
The text was updated successfully, but these errors were encountered:
👍 I like the idea.
It seems this would be pretty simple to do here: https://github.com/torchbox/django-pattern-library/blob/main/pattern_library/utils.py#L148. My preference would be for us to attempt to load the .yml file if .yaml doesn’t load, so projects can mix and match extensions.
PR welcome!
Sorry, something went wrong.
yml
Successfully merging a pull request may close this issue.
Issue Summary
When defining template context files (the YAML) files, these are only recognised when they use the full
.yaml
extension.When using the shorter
.yml
extension the template is not picking up the context file.This can be very confusing.
Steps to Reproduce
django-patter-library
enabletest.html
in one of the directories observed bydjango-pattern-library
with the contenttest.yaml
next to the template with the contentmv test.yaml test.yml
The text was updated successfully, but these errors were encountered: