Polymer element for the plotly.js library.
<plotly-plot> provides a thin, fully-functional interface to the core of the
library. The key properties of the plot,
all exposed as Polymer properties; updates to these properties via
automatically trigger redrawing.
All of the update methods provided with plotly.js have been exposed:
relayout. The other methods are also
available for dynamic updates:
Finally, the custom plotly-specific events are also replicated as Polymer events.
For thorough documentation, visit the project homepage.
Install the element with Bower by adding it to your project's dependencies in
bower.json, or install via NPM/Yarn by adding it to your
you install over NPM, make sure your dependencies are flat, as Polymer HTML
imports require it.
Import the element into your project by using an HTML import:
Polymer elements, and web components in general, depend on being able to "hide" their inner DOM from the rest of the page. This is accomplished through a set of functionality known as the "shadow DOM."
Polymer has two kinds of shadow DOM implementations: native shadow DOM, and a shim called "shady DOM." Native shadow DOM is newer and yields improved performance, but it has incomplete support in browsers outside the newest Chrome and can often cause problems with existing code. For this reason, shady DOM is still the default implementation in Polymer 1.x.
This is a library-level issue between plotly.js and the DOM. It does not have
to do with this element itself, and
<plotly-plot> can't do anything about it
until either plotly.js or the shadow DOM code change to accommodate one another.
In the mean time, if you're using
<plotly-plot>, make sure you
do not have
Polymer.dom = 'shadow' in the global Polymer settings of your
Element dependencies are managed via Bower for the front-end/polymer components, and NPM for everything else.
Installing NPM dependencies
$ npm install
Installing / updating Bower dependencies:
$ npm run bower:install$ npm run bower:update
Polylint can be used to take into account Polymer linting specificities.
$ npm run polylint
$ npm run eslint
Both can be run together:
$ npm run lint
Polyserve makes it easy to use the element while keeping Bower dependencies in line. It works well as a development server.
$ npm install -g polyserve
$ npm start
http://localhost:8080/components/plotly-plot/, shows the
index page of the element.
http://localhost:8080/components/plotly-plot/test/ (as served
by Polyserve) to run the tests.
The tests are implemented with web-component-tester. They can be run in a terminal:
$ npm test
npm test -- -l chromewill only run tests in chrome.
npm test -- -pwill keep the browsers alive after test runs (refresh to re-run).
npm test -- test/some-file.htmlwill test only the files you specify.
On every merge request in this repo, linting and tests will automatically be performed by travis-ci. Tagged versions are automatically released to NPM and Bower.