-
Notifications
You must be signed in to change notification settings - Fork 37
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
Background page structuring #171
Conversation
eslint complained about not using `await` and we don't want to return promises if we have no response.
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.
I've not looked at the differences between background and the new handlers, would've been nicer if the split was done first and then changes made so we can more easily see what's changing
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.
Left some comments. I mostly had a general look so far as I understand that this is pretty much a work in progress.
Co-Authored-By: Eric <SpyTec@users.noreply.github.com>
* Add webextension-polyfill@0.5.0 (background only) * Convert message listener to browser API + promises * Add basic message handler logic * Add no-return-await to eslint * Use explicit promise returns in message listener eslint complained about not using `await` and we don't want to return promises if we have no response. * Split out web request handler * Split out reload handler * Split out cache/global, use right polyfill file * Split out notification handling * chrome -> browser for most of the background stuff * Can't be clever about this one... * ? isn't a thing in jsdoc Co-Authored-By: Eric <SpyTec@users.noreply.github.com> * Directory eslint to remove per-file comments * Un-minify webext-polyfill * Handle background-bound global events more cleanly * Apply changes from master, misc. cleanup * Remove invalid jsdoc tag
Fixes #129, partially addresses #44.
TODOs:
{action: 'thing', ...options}
to['thing', {options}]
to free up theaction
key for use in handlerstb-
prefix and use a more descriptive convention (needs discussion)chrome.*
->browser.*
webextension APIs