Add unescape-safestr header to both fides-js fetch and privacy center calls #3706
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.
Closes #3606
Description Of Changes
#3600 made the
privacy-experience
endpoint support a headerUnescape-Safestr
. This updates fides-js and privacy-center calls to include that header. (See original issue for screenshots of what this looks like without the header)Code Changes
addCommonHeaders
now always includesUnescape-Safestr
Unescape-Safestr
Steps to Confirm
'
or&
. Can also edit the privacy experience copy to have those characters as well'
and&
s properly/fides-js-demo.html
to also see thatfides-js
renders your special characters 👍Pre-Merge Checklist
CHANGELOG.md