Refactor to use upcoming Django 6.0 CSP support #550
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Stormheg
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #532
In December, Django 6.0 is expected to be released.
One of the biggest features will be the built-in CSP support. This means that projects that previously used external CSP packages like django-csp will no longer need to rely on external tooling. CSP will be supported out-of-the-box 🎊
I've tested this tool, and I feel confident that we can replace our usage of django-csp with it. However, as Django 6.0 is not yet available, we cannot remove usage of django-csp.
This PR adds support for the coming Django 6.0 release, while keeping the existing django-csp functionality.
They will both be interchangeable, depending on whether it's a compatible Django version or not.