Do not HTML-escape help_text in Browsable API forms.
#3812
Merged
Conversation
This file contains 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
|
@sinitsynsv thanks, I see where this would come in handy, although I've never needed to do so. Would love to see what others think. |
|
Given the Django docs, this seems valid... https://docs.djangoproject.com/en/1.9/ref/models/fields/#help-text
Thanks for this @sinitsynsv! |
tomchristie
changed the title
help_text in Browsable API forms.
This was referenced Mar 9, 2017
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.
Some fields in django forms (SetPasswordForm for example, new_password1 field) have html help_text. I think in browsable api help_text must be rendered as is.