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

Going ES6 #16

Open
1 of 7 tasks
mkxml opened this issue Dec 17, 2015 · 1 comment
Open
1 of 7 tasks

Going ES6 #16

mkxml opened this issue Dec 17, 2015 · 1 comment
Labels
Milestone

Comments

@mkxml
Copy link
Owner

mkxml commented Dec 17, 2015

I've been thinking recently that making a switch over to pure JS (EcmaScript 6) would be a better choice to help contributors get used with the codebase.

The idea is to keep the current API and port the CoffeeScript code over to ES6.

To make that possible we would need to use the popular tool called babel since ES6 support is not yet complete in the majority of the browsers we want to support.

It's important to cover this issues:

  • It must be done in a specific branch and only merged when ready.
  • It must maintain the existent API, thus people using it right now won't notice the change when updating.
  • A styleguide should be used as base, Airbnb's JavaScript Guide is a great choice.
  • The test suite should be written using JS.
  • Document the code with jsdoc, most annotations can be easily ported from the currently used codo format.
  • The test process should remain the same.
  • The high level exposed grunt tasks should remain the same.
@mkxml
Copy link
Owner Author

mkxml commented Dec 17, 2015

Created es6-refactor branch for work related to this issue.

@mkxml mkxml added the es6 label Dec 17, 2015
@mkxml mkxml added this to the Version 1.0.0 milestone Dec 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant