How do you envision this feature/change to look/work like?
A special file should be designated for exporting DNR static rulesets that Plasmo will convert to json at build time.
What is the purpose of this change/feature? Why?
Working directly with json is a pain (no comments, variable substitutions, etc.)
My app uses a set of URLs that I need to generate corresponding rulesets for. Without a way to build the rulesets dynamically I have to either keep the json file updated manually, or use dynamic rules (which I don't actually need as the set of urls is not really dynamic).
This is mainly an issue for testing/development, when the rulesets might be changing a lot although the final version is fairly static
(OPTIONAL) Example implementations
No response
(OPTIONAL) Contribution
[ ] I would like to contribute to this RFC via a PR
Verify canary release
[X] I verified that the issue exists in plasmo canary release
Code of Conduct
[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.
How do you envision this feature/change to look/work like?
A special file should be designated for exporting DNR static rulesets that Plasmo will convert to json at build time.
What is the purpose of this change/feature? Why?
(OPTIONAL) Example implementations
No response
(OPTIONAL) Contribution
Verify canary release
plasmocanary releaseCode of Conduct