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.
My team uses CSP to secure a React app that uses ReactTooltip, but the way the style header is injected is incompatible, triggering a security warning about dynamic javascript injection.
This adds another build step that generates a separate static CSS file for inclusion, with a global configuration flag to avoid the injection.
No defaults have been changed, so the current example and usage story work the same, but I'm hoping a reasonable way to toggle the flag can be made other than to pass a prop
insecure={false}
to every component instance.What do you think?