Using the correct strict_min_version in extensions
wbamberg at mozilla.com
Thu Oct 26 15:41:57 UTC 2017
Michael, that's a very good idea.
The compat tables in the pages are built from JSON files, that are
maintained in GitHub and published as an npm package:
It's probably going to be easier to use the data directly, rather than
On Wed, Oct 25, 2017 at 11:43 PM, YF <yfdyh000 at gmail.com> wrote:
> 2017年10月26日星期四，Michael Buckley <support at codefisher.org> 写道：
>> Hi all,
>> Been finding it a lot of work to make sure I always use the correct min
>> version in my manifest file. So I wrote two scripts, one scraps the data
>> off the online docs and saves it to a local JSON file. The other takes
>> that JSON file and a folder with my extensions in it and does a rather
>> crude examination of the extension and gives a recommendation on what the
>> min version should be. I run it now at the end of my build script.
>> Feel free to use and modify as you see fit.
>> I think AMO itself should do this kind of check and give a warning if
>> there is a possible mistake. Is there a bug for that? I can't find one.
> https://github.com/mozilla/addons-linter/issues/1493 linter should
> report wrong min version for APIs usage, based on mdn/browser-compat-data
>> God Bless
> Best regards,
> Dev-addons mailing list
> Dev-addons at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Dev-addons