Add a configuration option to allow block tags to be excluded by regex #93
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.
Thanks for this plugin, which did almost exactly what we needed, apart from one issue, which this PR is an attempt to address.
The issue we had was that our project is using slippers, which means we have component tags in our templates with start/end block tags that don't follow the usual django convention for the end tag (
{% end<...> %}
). Instead they look something likeThis means that any component end tag on its own line gets marked as uncovered.
This PR adds a config option
exclude_blocks
which takes a list of regexes, similar toexclude_also
in the main coverage config, and allow us to specify patterns to match and exclude the content of block tags. With the following pyproject.toml config, we can now exclude any block tags that start with "/" (ie slippers component end tags).I didn't add a similar exclude option for text tags because there's additional complexity there since a text tag can span multiple lines (and I haven't seen issues that suggest it's a feature anyone needs yet)