Merge branch 'master' into ide

Author: rmarren1

.babelrc

@@ -1,3 +1,6 @@
 {
-    "extends": "./node_modules/dash-components-archetype/config/babel/babelrc"
+    "extends": "./node_modules/dash-components-archetype/config/babel/babelrc",
+    "plugins": [
+        "styled-jsx/babel"
+      ]
 }

CHANGELOG.md

@@ -2,21 +2,74 @@
 All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](http://semver.org/).
 
-## [0.24.0] - UNRELEASED
+## [0.27.0]
 ### Changed
 - `dash_core_components/__init__.py` now imports from python class files rather than generating classes at runtime,
 adding support for IDE autocomplete ect.
 
-## [0.23.0] - UNRELEASED
+## [0.26.0]
+### Added
+- New Tabs and Tab components! [#213](https://github.com/plotly/dash-core-components/pull/213#pullrequestreview-135893345)
+
+## [0.25.1]
+### Fixed
+- `__init__` version formatting for unpkg.
+
+## [0.25.0]
+### Added
+- `ConfirmDialog` and `ConfirmDialogProvider` components [#211](https://github.com/plotly/dash-core-components/pull/211)
+
+## [0.24.1]
+### Fixed
+- Improved DatePickerRange, fixing issues [#209](https://github.com/plotly/dash-core-components/issues/209) and [#152](https://github.com/plotly/dash-core-components/issues/152)
+- Link component now is a proper <a> tag so you can right click on it, and will scroll back to top. Fixes [#99](https://github.com/plotly/dash-core-components/issues/99), implemented in [#215](https://github.com/plotly/dash-core-components/pull/215)
+- Added `max_interval` prop to `Interval` component, fixing issue [#222](https://github.com/plotly/dash-core-components/issues/222)
+
+
+## [0.24.0]
 ### Added
 - Upgraded Plotly.js, the underlying library behind the
-`dash_core_components.Graph` component, to [version 1.38.0](https://github.com/plotly/plotly.js/releases/tag/v1.38.0).
-See https://github.com/plotly/plotly.js/releases/tag/v1.38.0 for the official notes.
+`dash_core_components.Graph` component, to [version 1.39.1](https://github.com/plotly/plotly.js/releases/tag/v1.39.1).
+See https://github.com/plotly/plotly.js/releases/tag/v1.39.1 for the official notes.
 
     Many of these features were funded directly by companies that rely on this library.
     If your organization or company would like to sponsor particular features or
     bug fixes in these open source libraries, please reach out: http://plot.ly/products/consulting-and-oem
 
+As part of plotly.js release:
+- Add support for on-graph text in scattergl traces [#2737](https://github.com/plotly/plotly.js/pull/2737), [#2783](https://github.com/plotly/plotly.js/pull/2783)
+- Add gridshape attribute to polar subplots with values 'circular' (the default) and 'linear' (to draw polygon grids) [#2739](https://github.com/plotly/plotly.js/pull/2739)
+- Add support for colorbar linked to marker.color values for splom,
+scatterpolar and scatterpolargl traces [#2681](https://github.com/plotly/plotly.js/pull/2681)
+- Revamp icon settings in custom mode bar buttons, allowing users to specify their own dimensions and SVG transforms [#2762](https://github.com/plotly/plotly.js/pull/2762)
+- Add plotlyServerURL config option [#2760](https://github.com/plotly/plotly.js/pull/2760)
+- Added no-WebGL warnings for graphs with scattergl, scatterpolargl, splom and parcoords traces [#2697](https://github.com/plotly/plotly.js/pull/2697)
+
+### Fixed
+As part of plotly.js release:
+- Fix Plotly.react's handling of changing auto-margins [#2681](https://github.com/plotly/plotly.js/pull/2681)
+- Make plotting/updating WebGL-based traces fail gracefully when WebGL isn't
+supported [#2697](https://github.com/plotly/plotly.js/pull/2697)
+- Fix mapbox layout layer updates [#2734](https://github.com/plotly/plotly.js/pull/2734)
+- Fix mapbox event inconsistencies [#2766](https://github.com/plotly/plotly.js/pull/2766)
+- Correctly emit plotly_relayout at end of scroll on mapbox subplots [#2709](https://github.com/plotly/plotly.js/pull/2709)
+- Fix scatter3d scalar hovertext handling [#2698](https://github.com/plotly/plotly.js/pull/2698)
+- Fix line decimation for segments crossing the viewport [#2705](https://github.com/plotly/plotly.js/pull/2705)
+- Fix surface trace contours when first level has length zero [#2712](https://github.com/plotly/plotly.js/pull/2712)
+- Fix contour(x|y|z).highlight partial settings [#2712](https://github.com/plotly/plotly.js/pull/2712)
+- Fix old date timezone precision in Chrome 67+ [#2747](https://github.com/plotly/plotly.js/pull/2747)
+- Fix x-only zoom moves when xaxis.fixedrange: true[#2776](https://github.com/plotly/plotly.js/pull/2776)
+- Fix colorbar edits for parcoords and histogram traces [#2681](https://github.com/plotly/plotly.js/pull/2681)
+- Fix bandwidth for single-value violins [#2775](https://github.com/plotly/plotly.js/pull/2775)
+- Make Plots.resize work when layout attribute is gone from graph div [#2710](https://github.com/plotly/plotly.js/pull/2710)
+- Fix colorscale attribute descriptions [#2658](https://github.com/plotly/plotly.js/pull/2658)    
+
+## [0.23.0]
+### Added
+- Upgraded Plotly.js, the underlying library behind the
+`dash_core_components.Graph` component, to [version 1.38.0](https://github.com/plotly/plotly.js/releases/tag/v1.38.0).
+See https://github.com/plotly/plotly.js/releases/tag/v1.38.0 for the official notes.
+
     - Add 3D `cone` traces to visualize vector fields [#2641](https://github.com/plotly/plotly.js/pull/2641), [#2647](https://github.com/plotly/plotly.js/pull/2647)
     - Add ability to interactively change length and rotate line shapes [#2594](https://github.com/plotly/plotly.js/pull/2594)
     - Add `toImageButtonOptions` config object to override to-image mode bar button options [#2607](https://github.com/plotly/plotly.js/pull/2607)

CONTRIBUTING.md

@@ -1,10 +1,28 @@
+# Contributing to dash-core-components
+
+## Getting Started
+
+Refer to the [readme](README.md) for installation and development instructions.
+
+## Contributions
+
+[Dash Core Components][] consist of pluggable components for creating interactive user interfaces. For generic HTML5 elements, see [Dash HTML Components][]. Contributions are welcome! This repository's open [issues][] are a good place to start. Another way to contribute is to [write your own components][] using the [Dash Components Archetype][].
+
+## Coding Style
+
+Please lint any additions to react components with `npm run lint`. Rules defined in [.eslintrc](.eslintrc) are inherited from [`dash-components-archetype`](https://github.com/plotly/dash-components-archetype)'s [eslintrc-react.json][]
+
+## Pull Request Guidelines
+
+Use the [GitHub flow][] when proposing contributions to this repository (i.e. create a feature branch and submit a PR against the master branch).
+
 ## Running the Tests
 
 In order to run the tests, you first need to have built the JavaScript
 `dash_core_components` library. You will need to build the library again if
 you've pulled from upstream otherwise you may be running with an out of date
-`bundle.js`. See the instructions for building `bundle.js` in the "Testing
-Locally" section of README.md.
+`bundle.js`. See the instructions for building `bundle.js` in the [Testing
+Locally](README.md#testing-locally) section of README.md.
 
 You also need to set the environment variable `TOX_PYTHON_27` and with the
 location of the Python 2 installations you want tox to use for creating the
@@ -30,3 +48,48 @@ If you encounter errors about Multi-server + Multi-processing when running under
 ```
 DASH_TEST_CHROMEPATH=/bin/google-chrome-beta DASH_TEST_PROCESSES=1 python -m unittest -v test.test_integration.Tests.test_inputs
 ```
+
+## Publishing New Components/Features
+
+For now, multiple steps are necessary for publishing to NPM and PyPi,
+respectively. TODO:
+[#5](https://github.com/plotly/dash-components-archetype/issues/5) will roll up publishing steps into one workflow.
+
+1. Create a pull request and tag the Plotly team (`@plotly/dash`) as well as an appropriate reviewer (frequent [contributors][] are a safe bet).
+2. After a review has been done and your changes have been approved, create a prerelease and comment in the PR. Version numbers should follow [semantic versioning][]. To create a prerelease:
+    * Add `rc1` to `version.py` (`./dash_core_components/version.py`) e.g. `0.13.0rc1`
+    * Add `-rc1` to `package.json` e.g. `0.13.0-rc1`
+    * Update the `unpkg` link in `./dash_core_components/__init__.py`, replacing `__version__` with your release candidate (e.g. `"0.13.0-rc1"`)
+    * Run `npm run publish-all`.
+        - If needed, ask @chriddyp to get NPM / PyPi package publishing access.
+        - If the `publish-all` script fails on the `twine` command, try running
+            ```sh
+            twine upload dist/dash_core_components-X.X.X.tar.gz # where xx.x.x is the version number
+            ```
+3. Comment in the PR with the prerelease version
+4. Update the top-level comment to include info about how to install, a summary of the changes, and a simple example. For a good example, see the [Confirmation Modal component][].
+    * This makes it easier for a community member to come in and try it out. As more folks review, it's harder to find the installation instructions deep in the PR
+    * Keep this top-level comment updated with installation instructions (e.g. the `pip install` command)
+5. Make a post in the [Dash Community Forum][]
+    * Title it `":mega: Announcement! New <Your Feature> - Feedback Welcome"`
+    * In the description, link to the PR and any relevant issue(s)
+    * Pin the topic so that it appears at the top of the forum for two weeks
+    * For a good example, see the [Confirmation Modal announcement][]
+    
+## Financial Contributions
+
+If your company wishes to sponsor development of open source dash components, please [get in touch][].
+
+[Dash Core Components]: https://dash.plot.ly/dash-core-components
+[Dash HTML Components]: https://github.com/plotly/dash-html-components
+[write your own components]: https://dash.plot.ly/plugins
+[Dash Components Archetype]: https://github.com/plotly/dash-components-archetype
+[issues]: https://github.com/plotly/dash-core-components/issues 
+[GitHub flow]: https://guides.github.com/introduction/flow/
+[eslintrc-react.json]: https://github.com/plotly/dash-components-archetype/blob/master/config/eslint/eslintrc-react.json
+[contributors]: https://github.com/plotly/dash-core-components/graphs/contributors
+[semantic versioning]: https://semver.org/
+[Dash Community Forum]: https://community.plot.ly/c/dash
+[Confirmation Modal component]: https://github.com/plotly/dash-core-components/pull/211#issue-195280462
+[Confirmation Modal announcement]: https://community.plot.ly/t/announcing-dash-confirmation-modal-feedback-welcome/11627
+[get in touch]: https://plot.ly/products/consulting-and-oem

MANIFEST.in

@@ -3,7 +3,7 @@ include dash_core_components/bundle.js.map
 include dash_core_components/metadata.json
 include dash_core_components/[email protected]
 include dash_core_components/[email protected]
-include dash_core_components/plotly-1.38.0.min.js
+include dash_core_components/plotly-1.39.1.min.js
 include dash_core_components/[email protected]
 include dash_core_components/[email protected]
 include dash_core_components/[email protected]

README.md

@@ -59,42 +59,18 @@ You have to maintain the list of components in `demo/Demo.react.js`.
 
 ### Code quality and tests
 
-#### To run lint and unit tests:
+### To run integration tests (test_integration.py)
+We run our integration tests on CircleCI with help from Tox. There’s a tox.ini file which holds the configuration, refer to [tox's documentation](http://tox.readthedocs.io/en/latest/index.html) for help. You may need to set environment variables in your terminal, like `TOX_PYTHON_27` to my version of python that I wanted tox to use. So running:
 
 ```sh
-$ npm test
+export TOX_PYTHON_27=python2
 ```
 
-#### To run unit tests and watch for changes:
+set the `TOX_PYTHON_27` env variable to point to `python2`, which is Python 2.7 running on my machine. 
+You could also look in `tox.ini` and see which tests it runs, and run those commands yourself: 
 
 ```sh
-$ npm run test-watch
-```
-
-#### To debug unit tests in a browser (Chrome):
-
-```sh
-$ npm run test-debug
-```
-
-1. Wait until Chrome launches.
-2. Click the "DEBUG" button in the top right corner.
-3. Open up Chrome Devtools (`Cmd+opt+i`).
-4. Click the "Sources" tab.
-5. Find source files
-  - Navigate to `webpack:// -> . -> spec/components` to find your test source files.
-  - Navigate to `webpack:// -> [your/repo/path]] -> dash-core-components -> src` to find your component source files.
-6. Now you can set breakpoints and reload the page to hit them.
-7. The test output is available in the "Console" tab, or in any tab by pressing "Esc".
-
-#### To run a specific test
-
-In your test, append `.only` to a `describe` or `it` statement:
-
-```javascript
-describe.only('Foo component', () => {
-    // ...
-});
+python -m unittest test.test_integration
 ```
 
 ### Testing your components in Dash
@@ -135,34 +111,7 @@ $ npm run uninstall-local
 
 ## Publishing
 
-For now, multiple steps are necessary for publishing to NPM and PyPi,
-respectively. TODO:
-[#5](https://github.com/plotly/dash-components-archetype/issues/5) will roll up
-publishing steps into one workflow.
-
-Ask @chriddyp to get NPM / PyPi package publishing access.
-
-1. Preparing to publish to NPM
-
-        # Bump the package version
-        $ npm version major|minor|patch
-
-        # Push branch and tags to repo
-        $ git push --follow-tags
-
-2. Preparing to publish to PyPi
-
-        # Bump the PyPi package to the same version
-        $ vi setup.py
-
-        # Commit to github
-        $ git add setup.py
-        $ git commit -m "Bump pypi package version to vx.x.x"
-
-3. Publish to npm and PyPi
-
-        $ npm run publish-all
-
+See the [Publishing New Components/Features](CONTRIBUTING.md#publishing-new-componentsfeatures) section of the Contributing guide for step-by-step instructions on publishing new components.
 
 ## Builder / Archetype
 

circle.yml

@@ -8,6 +8,8 @@ machine:
 
 dependencies:
     override:
+      - pip install setuptools --upgrade
+      - pip install virtualenv
       - pip install tox dash==0.23.1
       - npm install -g eslint
       - npm install --ignore-scripts

dash_core_components/ConfirmDialog.py

@@ -0,0 +1,65 @@
+# AUTO GENERATED FILE - DO NOT EDIT
+
+from dash.development.base_component import Component, _explicitize_args
+
+
+class ConfirmDialog(Component):
+    """A ConfirmDialog component.
+ConfirmDialog is used to display the browser's native "confirm" modal,
+with an optional message and two buttons ("OK" and "Cancel").
+This ConfirmDialog can be used in conjunction with buttons when the user
+is performing an action that should require an extra step of verification.
+
+Keyword arguments:
+- id (string; optional)
+- message (string; optional): Message to show in the popup.
+- submit_n_clicks (number; optional): Number of times the submit button was clicked
+- submit_n_clicks_timestamp (number; optional): Last time the submit button was clicked.
+- cancel_n_clicks (number; optional): Number of times the popup was canceled.
+- cancel_n_clicks_timestamp (number; optional): Last time the cancel button was clicked.
+- displayed (boolean; optional): Set to true to send the ConfirmDialog.
+
+Available events: """
+    @_explicitize_args
+    def __init__(self, id=Component.UNDEFINED, message=Component.UNDEFINED, submit_n_clicks=Component.UNDEFINED, submit_n_clicks_timestamp=Component.UNDEFINED, cancel_n_clicks=Component.UNDEFINED, cancel_n_clicks_timestamp=Component.UNDEFINED, displayed=Component.UNDEFINED, **kwargs):
+        self._prop_names = ['id', 'message', 'submit_n_clicks', 'submit_n_clicks_timestamp', 'cancel_n_clicks', 'cancel_n_clicks_timestamp', 'displayed']
+        self._type = 'ConfirmDialog'
+        self._namespace = 'dash_core_components'
+        self._valid_wildcard_attributes =            []
+        self.available_events = []
+        self.available_properties = ['id', 'message', 'submit_n_clicks', 'submit_n_clicks_timestamp', 'cancel_n_clicks', 'cancel_n_clicks_timestamp', 'displayed']
+        self.available_wildcard_properties =            []
+
+        _explicit_args = kwargs.pop('_explicit_args')
+        _locals = locals()
+        _locals.update(kwargs)  # For wildcard attrs
+        args = {k: _locals[k] for k in _explicit_args if k != 'children'}
+
+        for k in []:
+            if k not in args:
+                raise TypeError(
+                    'Required argument `' + k + '` was not specified.')
+        super(ConfirmDialog, self).__init__(**args)
+
+    def __repr__(self):
+        if(any(getattr(self, c, None) is not None
+               for c in self._prop_names
+               if c is not self._prop_names[0])
+           or any(getattr(self, c, None) is not None
+                  for c in self.__dict__.keys()
+                  if any(c.startswith(wc_attr)
+                  for wc_attr in self._valid_wildcard_attributes))):
+            props_string = ', '.join([c+'='+repr(getattr(self, c, None))
+                                      for c in self._prop_names
+                                      if getattr(self, c, None) is not None])
+            wilds_string = ', '.join([c+'='+repr(getattr(self, c, None))
+                                      for c in self.__dict__.keys()
+                                      if any([c.startswith(wc_attr)
+                                      for wc_attr in
+                                      self._valid_wildcard_attributes])])
+            return ('ConfirmDialog(' + props_string +
+                   (', ' + wilds_string if wilds_string != '' else '') + ')')
+        else:
+            return (
+                'ConfirmDialog(' +
+                repr(getattr(self, self._prop_names[0], None)) + ')')