Hard to integrate with CSP rules in place

[sgelis]

django-silk makes extensive use of inline <style> and <script> tags in its templates. This makes it very hard to :

• Override default behavior of style and/or scripts (whole template needs to be overridden).
  -Apply CSP rules properly on a project that wants to use Silk and proper CSP rules (almost all templates must be overridden to add nonce attributes all over the place).

Was there a historical reason to put all these <style> and <script> tags inline? Would a PR addressing this issue be considered OK for maintainers?

[Archmonger]

Not sure about the historical reasoning, but many django repositories use static files for CSS/JS. I see no reason why we can't do that here.

Feel free to PR this behavior.

[sshishov]

Using <style> and <script> tags are the proper approach actually. We should not use inline styles or scripts.

The solution would be here to add the support for nonce to be injected in every style or script in the templates if it is available in the context, for instance.

This is how all other third party apps added the support for CSP3.