Use ES6 imports #12
Merged
Use ES6 imports #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ear future. Remove TouchPanner options as well for simplicity, as it's no longer in use.
|
@lincolnfrog thanks for reviewing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal of this was to do initial ES6-ification of these modules with import/export, not a full ES6-ification of everything. Wanting to use sensor polyfill for adding the Generic Sensors API (via #10), which would need a ES6 module loader anyway, so this is a good time as any.
Also removed the vestigial TouchPanner (outside of polyfill's jurisdiction), as well as a vestigial Util.race (used in webvr-polyfill, not here).