Allow for a customizable fallback mapper #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I'm not sure whether you're accepting pull requests or not. If you're not, feel free to close!
My thinking here is to be able to set a
fallback_mapper
in the settings that defaults todj_angles.mappers.django.map_include
.What one would be able to able to accomplish by switching the fallback mapper is to use their favorite component library as fallback instead of
{% include %}
.So for example, assuming django bird, with the appropriate mapper:
<dj-partial />
would be mapped to{% bird partial %}{% endbird %}
instead of{% include 'partial.html' %}
I'm opening this as draft, as if that's something you'd be interested in, documentation would be needed