GitHub user felizbear reopened a pull request:

    https://github.com/apache/zeppelin/pull/1639

    [ZEPPELIN-1667] add support for es6

    ### What is this PR for?
    This PR adds support for the current ECMAScript standard 
[es6](http://www.ecma-international.org/ecma-262/6.0/) via 
[babel](http://babeljs.io/) 
([babel-grunt](https://github.com/babel/grunt-babel) plugin)
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    * [x] - Add babel presets for es6 (aka es2015) and object spread operator
    * [x] - Add eslint rules to lint es6 correctly
    * [x] - Add `babel` task to grunt and modify `serve`, `test` and `build` 
tasks
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-1667
    
    ### How should this be tested?
    1. Run `grunt serve` and make sure it works properly (including reload on 
change)
    2. Run `grunt test` and make sure tests pass
    3. Run `grunt build` and make sure it builds and runs correctly
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/felizbear/zeppelin frontend-es2015

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1639.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1639
    
----
commit 971f05f9eaeccdaeec351eacd7aa2b9c6d25792a
Author: felizbear <i...@nflabs.com>
Date:   2016-11-15T08:35:49Z

    add dependencies on grunt-babel and babel presets

commit 3d9531b2789769e65fba5de92dda5c60c37a77db
Author: felizbear <i...@nflabs.com>
Date:   2016-11-15T08:29:23Z

    update eslintrc to enable linting es6

commit 192cf00f9ae613bb77777a3985eef234e7d23f10
Author: felizbear <i...@nflabs.com>
Date:   2016-11-15T02:17:41Z

    add babel task to gruntfile

commit fc87a33da14ec4cc15ccae5989fb22063fb402f2
Author: felizbear <i...@nflabs.com>
Date:   2016-11-18T01:12:12Z

    increase heap size in travis CI

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to