Skip to content
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

Proposal: module for WebExtensions schemas #89

Closed
asamuzaK opened this issue May 5, 2019 · 3 comments · May be fixed by #94
Closed

Proposal: module for WebExtensions schemas #89

asamuzaK opened this issue May 5, 2019 · 3 comments · May be fixed by #94

Comments

@asamuzaK
Copy link

asamuzaK commented May 5, 2019

Hi,
I created a module that fetched and saved the WebExtensions schema directly from hg.mozilla.org.
asamuzaK/webext-schema: WebExtensions schemas fetched from hg.mozilla.org

It is still under development, but I think that with this module, sinon-chrome will no longer has to worry about WebExtensions schemas.
And this module should fix #63 and #87.

At this time, I can't verify that it actually works with sinon-chrome for the #88 issue, but as far as I've tried, it seems to work fine.
Test code webext-schema/schema.test.js at master · asamuzaK/webext-schema

Please send me your feedback on whether or not to implement this module to sinon-chrome.
If you think it's acceptable, I'll send a PR later.

Thanks.

@ariasuni
Copy link

Any news about this? I can’t use sinon-chrome because it doesn’t support browser.menus, for example.

@stoically
Copy link
Contributor

My webextensions-schema might also be of interest, it automatically fetches the latest stable schema. I've built it as basis for webextensions-api-mock.

@asamuzaK
Copy link
Author

asamuzaK commented Feb 8, 2020

I'll close this issue.
webext-schema now creates the stubbed browser API

@asamuzaK asamuzaK closed this as completed Feb 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants