Merge pull request #2734 from jasongrout/format

Format files with prettier

Author: jasongrout

.vscode/extensions.json

@@ -1,5 +1,3 @@
 {
-    "recommendations": [
-      "dbaeumer.vscode-eslint"
-    ]
+  "recommendations": ["dbaeumer.vscode-eslint", "esbenp.prettier-vscode"]
 }

docs/source/changelog.md

@@ -1,10 +1,8 @@
-ipywidgets changelog
-====================
+# ipywidgets changelog
 
 A summary of changes in ipywidgets. For more detailed information, see the issues and pull requests for the appropriate milestone on [GitHub](https://github.com/jupyter-widgets/ipywidgets).
 
-7.5
----
+## 7.5
 
 To see the full list of pull requests and issues, see the [7.5 milestone](https://github.com/jupyter-widgets/ipywidgets/milestone/268?closed=1) on GitHub.
 
@@ -19,20 +17,17 @@ Changes include:
 
 Custom widget maintainers will need to update their `@jupyter-widgets/base` dependency version to work in JupyterLab 1.0. For example, if you had a dependency on `@jupyter-widgets/base` version `^1.1`, update to `^1.1 || ^2` for your widget to work in classic notebook, JupyterLab 0.35, and JupyterLab 1.0. See [#2472](https://github.com/jupyter-widgets/ipywidgets/pull/2472) for background.
 
-
-7.4
----
+## 7.4
 
 To see the full list of pull requests and issues, see the [7.4 milestone](https://github.com/jupyter-widgets/ipywidgets/milestone/26?closed=1) on GitHub.
 
 Changes include:
 
 - New `Video` and `Audio` widgets have been introduced. [#2162](https://github.com/jupyter-widgets/ipywidgets/pull/2162)
-We updated the `@jupyter-widgets/controls` widget specification version to `1.4.0`, leading to the version bump to 7.4.
+  We updated the `@jupyter-widgets/controls` widget specification version to `1.4.0`, leading to the version bump to 7.4.
 - The use of mappings for the `options` attribute of selection widgets is deprecated. [#2130](https://github.com/jupyter-widgets/ipywidgets/pull/2130)
 
-7.3
----
+## 7.3
 
 To see the full list of pull requests and issues, see the [7.3 milestone](https://github.com/jupyter-widgets/ipywidgets/milestone/26?closed=1) on GitHub.
 
@@ -52,8 +47,7 @@ Changes include:
 
 - The license information has been consolidated into the LICENSE file, and the COPYING.md file is removed. If you are repackaging ipywidgets or widgetsnbextension, please make sure to include LICENSE instead of COPYING.md. ([#2133](https://github.com/jupyter-widgets/ipywidgets/pull/2133), [#2048](https://github.com/jupyter-widgets/ipywidgets/pull/2048), [#1701](https://github.com/jupyter-widgets/ipywidgets/issues/1701), [#1706](https://github.com/jupyter-widgets/ipywidgets/pull/1706))
 
-7.2
----
+## 7.2
 
 To see the full list of pull requests and issues, see the [7.2 milestone](https://github.com/jupyter-widgets/ipywidgets/milestone/25?closed=1) on GitHub.
 
@@ -67,6 +61,7 @@ User-visible changes include:
 - `link` and `dlink` are now exported from ipywidgets for convenience, so that you can import them directly from ipywidgets instead of needing to import them from traitlets. ([#1923](https://github.com/jupyter-widgets/ipywidgets/pull/1923))
 - A new option `manual_name` has been added to `interact_manual()` to change the name of the update button, for example `interact_manual(manual_name='Update')`. ([#1924](https://github.com/jupyter-widgets/ipywidgets/pull/1923))
 - The Output widget now has a `.capture()` method, which returns a decorator to capture the output of a function.
+
   ```python
   from ipywidgets import Output
   out = Output()
@@ -75,7 +70,9 @@ User-visible changes include:
   def f():
     print('This output is captured')
   ```
+
   The `.capture()` method has a `clear_output` boolean argument to automatically clear the output every time the function is run, as well as a `wait` argument corresponding to the `clear_output` wait argument. ([#1934](https://github.com/jupyter-widgets/ipywidgets/pull/1934))
+
 - The Output widget has much more comprehensive documentation in its own section. ([#2020](https://github.com/jupyter-widgets/ipywidgets/pull/2020))
 - Installing `widgetsnbextension` now automatically enables the nbextension in Jupyter Notebook 5.3 or later. ([#1911](https://github.com/jupyter-widgets/ipywidgets/pull/1911))
 - The default rendering of a widget if widgets are not installed is now a short description of the widget in text instead of a much longer HTML message. ([#2007](https://github.com/jupyter-widgets/ipywidgets/pull/2007))
@@ -86,20 +83,17 @@ Changes for developers include:
 - The html manager now exposes a way to specify which JavaScript file is fetched for a package and the loader used to fetch the library. ([#1995](https://github.com/jupyter-widgets/ipywidgets/pull/1995), [#1998](https://github.com/jupyter-widgets/ipywidgets/pull/1998))
 - The `@jupyter-widgets/controls` widget specification version was bumped to `1.2.0`. Changes include the FloatLogSlider widget and more specific documentation about array element types. ([#2017](https://github.com/jupyter-widgets/ipywidgets/pull/2017))
 
-7.1
----
+## 7.1
 
 To see the full list of pull requests and issues, see the [7.1 milestone](https://github.com/jupyter-widgets/ipywidgets/milestone/23?closed=1) on GitHub.
 
 We updated the `@jupyter-widgets/controls` widget specification version to `1.1.0`, leading to the version bump to 7.1. The new widget model specification now includes new `description_width` and `font_weight` attributes for the `ToggleButtonsStyle` widget. There are also other bugfixes in this release.
 
-7.0.x patch releases
---------------------
+## 7.0.x patch releases
 
 See the GitHub milestones for the [7.0.1](https://github.com/jupyter-widgets/ipywidgets/milestone/16?closed=1), [7.0.2](https://github.com/jupyter-widgets/ipywidgets/milestone/17?closed=1), [7.0.3](https://github.com/jupyter-widgets/ipywidgets/milestone/18?closed=1), [7.0.4](https://github.com/jupyter-widgets/ipywidgets/milestone/20?closed=1), and [7.0.5](https://github.com/jupyter-widgets/ipywidgets/milestone/21?closed=1) releases for bugfixes in these releases.
 
-7.0
----
+## 7.0
 
 To see the full list of pull requests and issues, see the [7.0 milestone](https://github.com/jupyter-widgets/ipywidgets/milestone/12?closed=1) on GitHub.
 
@@ -111,7 +105,7 @@ Major user-visible changes in ipywidgets 7.0 include:
 - The `layout` and `style` traits can be set with a dictionary for convenience, which will automatically converted to a Layout or Style object, like `IntSlider(layout={'width': '100%'}, style={'handle_color': 'lightgreen'})`. ([#1253](https://github.com/jupyter-widgets/ipywidgets/pull/1253))
 - The Select widget now is a listbox instead of a dropdown, reverting back to the pre-6.0 behavior. ([#1238](https://github.com/jupyter-widgets/ipywidgets/pull/1238))
 - The Select and SelectMultiple widgets now have a `rows` attribute for the number of rows to display, consistent with the Textarea widget. The `layout.height` attribute overrides this to control the height of the widget. ([#1250](https://github.com/jupyter-widgets/ipywidgets/pull/1250))
-- Selection widgets (`Select`, `Dropdown`, `ToggleButtons`, etc.) have new `.value`, `.label`, and `.index` traits to make it easier to access or change the selected option.  ([#1262](https://github.com/jupyter-widgets/ipywidgets/pull/1262), [#1513](https://github.com/jupyter-widgets/ipywidgets/pull/1513))
+- Selection widgets (`Select`, `Dropdown`, `ToggleButtons`, etc.) have new `.value`, `.label`, and `.index` traits to make it easier to access or change the selected option. ([#1262](https://github.com/jupyter-widgets/ipywidgets/pull/1262), [#1513](https://github.com/jupyter-widgets/ipywidgets/pull/1513))
 - Selection container widgets (`Accordion`, `Tabs`) can have their `.selected_index` set to `None` to deselect all items. ([#1495](https://github.com/jupyter-widgets/ipywidgets/pull/1495))
 - The `Play` widget range is now inclusive (max value is max, instead of max-1), to be consistent with Sliders
 - The `Play` widget now has an optional repeat toggle button (visible by default). ([#1190](https://github.com/jupyter-widgets/ipywidgets/pull/1190))
@@ -124,7 +118,7 @@ Major user-visible changes in ipywidgets 7.0 include:
 - ToggleButtons have a new `.style.button_width` attribute to set the CSS width of the buttons. Set this to `'initial'` to have buttons that individually size to the content width. ([#1257](https://github.com/jupyter-widgets/ipywidgets/pull/1257))
 - The `readout_format` attribute of number sliders now validates its argument. ([#1550](https://github.com/jupyter-widgets/ipywidgets/pull/1550))
 - The `IntRangeSlider` widget now has a `.readout_format` trait to control the formatting of the readout. ([#1446](https://github.com/jupyter-widgets/ipywidgets/pull/1446))
-- The `Text`, `Textarea`, `IntText`, `BoundedIntText`, `FloatText`, and `BoundedFloatText` widgets all gained a `continuous_update` attribute (defaults to `True` for `Text` and `TextArea`, and `False` for the others).  ([#1545](https://github.com/jupyter-widgets/ipywidgets/pull/1545))
+- The `Text`, `Textarea`, `IntText`, `BoundedIntText`, `FloatText`, and `BoundedFloatText` widgets all gained a `continuous_update` attribute (defaults to `True` for `Text` and `TextArea`, and `False` for the others). ([#1545](https://github.com/jupyter-widgets/ipywidgets/pull/1545))
 - The `IntText`, `BoundedIntText`, `FloatText`, and `BoundedFloatText` widgets are now rendered as HTML number inputs, and have a `step` attribute that controls the resolution. ([#1545](https://github.com/jupyter-widgets/ipywidgets/pull/1545))
 - The `Text.on_submit` callback is deprecated; instead, set `continuous_update` to `False` and observe the `value` attribute: `mywidget.observe(callback, 'value')`. The `Textarea.scroll_to_bottom` method was removed. ([#1545](https://github.com/jupyter-widgets/ipywidgets/pull/1545))
 - The `msg_throttle` attribute on widgets is now gone, and the code has a hardcoded message throttle equivalent to `msg_throttle=1`. ([#1557](https://github.com/jupyter-widgets/ipywidgets/pull/1557))
@@ -151,24 +145,23 @@ If you are developing a custom widget or widget manager, here are some major cha
   - Custom widget managers are now responsible completely for loading widget model and view classes. Widget managers should provide an output model and view class appropriate for their environment so that the `Output` widget works. ([#1313](https://github.com/jupyter-widgets/ipywidgets/pull/1313))
   - The widget manager `clear_state` method no longer has a `commlessOnly` argument. All models in the widget manager will be closed and cleared when `clear_state` is called. ([#1354](https://github.com/jupyter-widgets/ipywidgets/pull/1354))
 
-6.0
----
+## 6.0
 
 Major user-visible changes in ipywidgets 6.0 include:
 
- - Rendering of Jupyter interactive widgets in various web contexts
+- Rendering of Jupyter interactive widgets in various web contexts
 
-     sphinx documentation: http://ipywidgets.readthedocs.io/en/latest/examples/Widget%20List.html
-     nbviewer: http://nbviewer.jupyter.org/github/jupyter-widgets/ipywidgets/blob/master/docs/source/examples/Widget%20List.ipynb
-     Static web pages: http://jupyter.org/widgets
+  sphinx documentation: http://ipywidgets.readthedocs.io/en/latest/examples/Widget%20List.html
+  nbviewer: http://nbviewer.jupyter.org/github/jupyter-widgets/ipywidgets/blob/master/docs/source/examples/Widget%20List.ipynb
+  Static web pages: http://jupyter.org/widgets
 
- -  Addition of a DatePicker widget in the core widget collection.
+- Addition of a DatePicker widget in the core widget collection.
 
- - Changes to the automatic control generation syntax in @interact, inspired by the Sage interact syntax.
+- Changes to the automatic control generation syntax in @interact, inspired by the Sage interact syntax.
 
- - Removal of APIs which had been deprecated in 5.0, including top-level styling in attributes of DOMWidgets and some corner cases in the behavior of `@interact`.
+- Removal of APIs which had been deprecated in 5.0, including top-level styling in attributes of DOMWidgets and some corner cases in the behavior of `@interact`.
 
- - A new API for custom styling of widgets is provided, through a top-level `style` attribute. For example, the color of a slider handler can be set by `slider.style.handle_color`.
+- A new API for custom styling of widgets is provided, through a top-level `style` attribute. For example, the color of a slider handler can be set by `slider.style.handle_color`.
 
 - Removal of the Proxy and PlaceProxy widgets.
 
@@ -182,15 +175,16 @@ Major user-visible changes in ipywidgets 6.0 include:
 
 - Removal of the `button_style` attribute of the Dropdown widget
 
- - Addition of an OutputWidget for capturing output and rich display objects. @interact has changed to use an OutputWidget for function output instead of overwriting the output area of a cell.
+- Addition of an OutputWidget for capturing output and rich display objects. @interact has changed to use an OutputWidget for function output instead of overwriting the output area of a cell.
 
- - The jupyter-js-widgets Javascript implementation now relies on the PhosphorJS framework for the management of rich layout and a better integration of JupyterLab.
+- The jupyter-js-widgets Javascript implementation now relies on the PhosphorJS framework for the management of rich layout and a better integration of JupyterLab.
 
 - Numerous bug fixes.
 
-*Note for custom widget authors:*
+_Note for custom widget authors:_
+
+ipywidgets 6.0 breaks backward compatibility with respect to the handling of default values of the JavaScript side. Now, the default values for core widget models are specified with a `default()` method returning a dictionary instead of a `default` dictionary attribute. If you want your library to be backwards compatible with ipywidgets 5.x, you could use [\_.result](http://underscorejs.org/#result) like this:
 
-ipywidgets 6.0 breaks backward compatibility with respect to the handling of default values of the JavaScript side. Now, the default values for core widget models are specified with a `default()` method returning a dictionary instead of a `default` dictionary attribute. If you want your library to be backwards compatible with ipywidgets 5.x, you could use  [_.result](http://underscorejs.org/#result) like this:
 ```javascript
 ...
 defaults: function() {
@@ -201,21 +195,17 @@ defaults: function() {
 ...
 ```
 
-
 This should not have an impact when using your custom widgets in the classic notebook, but will be really important when deploying your interactive widgets in web contexts.
 
-5.x
----
+## 5.x
 
-4.1.x
------
+## 4.1.x
 
 ### 4.1.1
 
 ### 4.1.0
 
-4.0.x
------
+## 4.0.x
 
 ### 4.0.3
 

examples/web1/index.js

@@ -3,70 +3,72 @@ var WidgetManager = require('./manager').WidgetManager;
 
 require('@jupyter-widgets/controls/css/widgets.css');
 
-document.addEventListener("DOMContentLoaded", function(event) {
-    var manager = new WidgetManager(document.body);
+document.addEventListener('DOMContentLoaded', function(event) {
+  var manager = new WidgetManager(document.body);
 
-    /**
-     * Helper function for creating and displaying widgets.
-     * @return {Promise<WidgetView>}
-     */
-    function createWidget(widgetType, value, description) {
-
-        // Create the widget model.
-        return manager.new_model({
-            model_module: '@jupyter-widgets/controls',
-            model_name: widgetType + 'Model',
-            model_id: 'widget-1'
+  /**
+   * Helper function for creating and displaying widgets.
+   * @return {Promise<WidgetView>}
+   */
+  function createWidget(widgetType, value, description) {
+    // Create the widget model.
+    return manager
+      .new_model({
+        model_module: '@jupyter-widgets/controls',
+        model_name: widgetType + 'Model',
+        model_id: 'widget-1'
         // Create a view for the model.
-        }).then(function(model) {
-            console.log(widgetType + ' model created');
+      })
+      .then(function(model) {
+        console.log(widgetType + ' model created');
 
-            model.set({
-                description: description || '',
-                value: value,
-            });
+        model.set({
+          description: description || '',
+          value: value
+        });
 
-            return  manager.create_view(model);
-        }, console.error.bind(console))
-        .then(function(view) {
-            console.log(widgetType + ' view created');
-            manager.display_view(null, view);
-            return view;
-        }, console.error.bind(console));
-    }
+        return manager.create_view(model);
+      }, console.error.bind(console))
+      .then(function(view) {
+        console.log(widgetType + ' view created');
+        manager.display_view(null, view);
+        return view;
+      }, console.error.bind(console));
+  }
 
-    var defaultHTML = 'test <b>text</b>';
-    var textArea = createWidget('Textarea', defaultHTML, 'HTML:');
-    var html = createWidget('HTML', defaultHTML);
+  var defaultHTML = 'test <b>text</b>';
+  var textArea = createWidget('Textarea', defaultHTML, 'HTML:');
+  var html = createWidget('HTML', defaultHTML);
 
-    // Create a link model.
-    manager.new_model({
-        model_module: '@jupyter-widgets/controls',
-        model_name: 'LinkModel',
-        model_id: 'widget-2',
-        state: {
-            'source': null,
-            'target': null
-        }
-    // Set the link model state.
-    }).then(function(link) {
-        console.log('link created');
+  // Create a link model.
+  manager
+    .new_model({
+      model_module: '@jupyter-widgets/controls',
+      model_name: 'LinkModel',
+      model_id: 'widget-2',
+      state: {
+        source: null,
+        target: null
+      }
+      // Set the link model state.
+    })
+    .then(function(link) {
+      console.log('link created');
 
-        return Promise.all([textArea, html]).then(
-            function(models) {
-                console.log('setting link');
-                var textArea = models[0];
-                var html = models[1];
-                link.set({
-                    'source': [textArea.model, 'value'],
-                    'target': [html.model, 'value']
-                });
-                link.save_changes();
-                console.log('link set');
-            }
-        );
-    }).then(function() {
-        var event = new Event('widgetsRendered');
-        document.dispatchEvent(event);
+      return Promise.all([textArea, html]).then(function(models) {
+        console.log('setting link');
+        var textArea = models[0];
+        var html = models[1];
+        link.set({
+          source: [textArea.model, 'value'],
+          target: [html.model, 'value']
+        });
+        link.save_changes();
+        console.log('link set');
+      });
+    })
+    .then(function() {
+      var event = new Event('widgetsRendered');
+      document.dispatchEvent(event);
     });
 });