Chart.js 2.8.0 and CSP compliance #54
Open
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
|
close #58 |
|
Any update on getting this merged @airblade? This will fix CSP issues and update to Chart.js 2.8.0 |
Owner
|
Unfortunately I don't use this any more and don't have the time to maintain it. I'm happy to hand it over to someone. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
We're using chartjs-ror with a strict CSP configuration. Chart.js 2.8 provides an option to disable css injection and provides a separate stylesheet.
This PR updates Chart.js, provides the stylesheet as an scss file and implements an option to disable css injection. I assumed a Chart.js version update might indicate a gem version update, too. I haven't found any issues with just dropping 2.8.0 in, tests run without errors.
Maybe there's a better way to implement this, I'm not married to this PR :)