Expose default clean_content_tags as module constant#118
Merged
messense merged 1 commit intomessense:mainfrom Mar 24, 2026
Merged
Expose default clean_content_tags as module constant#118messense merged 1 commit intomessense:mainfrom
messense merged 1 commit intomessense:mainfrom
Conversation
messense
approved these changes
Mar 24, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Ammonia already exposes
clone_clean_content_tags()on the builder, but nh3 didn't surface it as a Python-accessible constant. I needed to check the defaults while working withclean_content_tagsand noticed this was missing.Adds
CLEAN_CONTENT_TAGSfollowing the same pattern asALLOWED_TAGS,ALLOWED_ATTRIBUTES, andALLOWED_URL_SCHEMES.Closes #116