[GitHub] zeppelin pull request #2267: [MINOR] Verbose logging in zeppelin-web

[1ambda]

GitHub user 1ambda opened a pull request:

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

    [MINOR] Verbose logging in zeppelin-web

    ### What is this PR for?
    
    Verbose logging in zeppelin-web. See the screenshot below.
    
    - Remove the first `console.log` since it's already printed in the 
following statement.
    
    ### What type of PR is it?
    [Improvement]
    
    ### Todos
    
    NONE
    
    ### What is the Jira issue?
    
    MINOR
    
    ### How should this be tested?
    
    1. start Zeppelin in dev mode (`:9000`)
    2. open browser console
    
    ### Screenshots (if appropriate)
    
    #### Before
    
    <img width="841" alt="screen shot 2017-04-20 at 7 12 18 pm" 
src="https://cloud.githubusercontent.com/assets/4968473/25227897/352e49a8-2605-11e7-98dc-58c3810e1971.png";>
    
    #### After
    
    <img width="810" alt="screen shot 2017-04-20 at 8 06 51 pm" 
src="https://cloud.githubusercontent.com/assets/4968473/25227904/37be8db8-2605-11e7-84cb-bc981d85d04d.png";>
    
    ### Questions:
    * Does the licenses files need update?
    * Is there breaking changes for older versions?
    * Does this needs documentation?


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

    $ git pull https://github.com/1ambda/zeppelin MINOR/verbose-logging

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

    https://github.com/apache/zeppelin/pull/2267.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 #2267
    
----
commit 7448e52ddcb76443f60c37961da503a719923cb2
Author: 1ambda <1am...@gmail.com>
Date:   2017-04-20T11:05:10Z

    fix: Use console.log with JSON.parse

----


---
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.
---