Repository navigation
Replies: 3 comments
|
Not a maintainer, but I traced it in the source, so you can link the code for reviewers.
Both are framework-mode only. If your extension uses data or declarative mode ( |
1. Definitive Answer for Reviewers & Security AuditsNo user-provided data is ever passed to Here is the exact architectural proof you can link and quote in your review notes:
2. Why the Linter Warning HappensAutomated store linters (such as Mozilla’s Because Even if you explain in a 3. How to Completely Eliminate the Warning in WebpackYou can safely strip the offending Solution A: Webpack
|
|
Ran into this exact linter warning when packaging a React extension for the Chrome and Firefox addon stores. You can safely confirm to extension reviewers that zero user-provided input ever touches Here is the exact explanation you can include in your reviewer notes:
For store reviewers, adding a short note like this in the submission form usually gets it approved right away:
Hope that clears it up for your extension review! |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I have a web extension which uses React and React router to render browser action and I get this warning upon submission:
The offending segment looks like this (webpack bundler output):
I assume it's some RR internals and therefore operates on the route data known at build time, which never changes at runtime.
But I need a definitive answer from maintainers (so I could link it in readme for reviewers) for this question:
Are you absolutely sure no user-provided data is passed to this function at runtime?
All reactions