-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: add note forbidding allowance of user input of JS #1394
base: main
Are you sure you want to change the base?
Conversation
Hello! 👋 This repository uses Auto for releasing packages using PR labels. ✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe change it as suggested to also highlight that the plugin developer should not enter any kind of code that will be executed in the browser or at the server side. So we should not allow the user to enter golang code either. Or code that gets executed on potential third party services.
Co-authored-by: Marcus Andersson <marcus.andersson@grafana.com>
Add note to best practices doc telling plugin developers not to allow the plugin's users to input random JS.
Fixes: #1233