Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cwdoh/google-map-heatmap
Polymer element providing a solution to support heatmap of google-map element.
https://github.com/cwdoh/google-map-heatmap
Last synced: 4 days ago
JSON representation
Polymer element providing a solution to support heatmap of google-map element.
- Host: GitHub
- URL: https://github.com/cwdoh/google-map-heatmap
- Owner: cwdoh
- License: mit
- Created: 2015-08-18T04:40:06.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2015-08-18T04:44:00.000Z (over 9 years ago)
- Last Synced: 2024-11-17T19:48:50.146Z (about 1 month ago)
- Language: HTML
- Size: 1.6 MB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# google-map-heatmap
An element providing a starting point for your own reusable Polymer elements.
## Dependencies
Element dependencies are managed via [Bower](http://bower.io/). You can
install that via:npm install -g bower
Then, go ahead and download the element's dependencies:
bower install
## Playing With Your Element
If you wish to work on your element in isolation, we recommend that you use
[Polyserve](https://github.com/PolymerLabs/polyserve) to keep your element's
bower dependencies in line. You can install it via:npm install -g polyserve
And you can run it via:
polyserve
Once running, you can preview your element at
`http://localhost:8080/components/google-map-heatmap/`, where `google-map-heatmap` is the name of the directory containing it.## Testing Your Element
Simply navigate to the `/test` directory of your element to run its tests. If
you are using Polyserve: `http://localhost:8080/components/google-map-heatmap/test/`### web-component-tester
The tests are compatible with [web-component-tester](https://github.com/Polymer/web-component-tester).
Install it via:npm install -g web-component-tester
Then, you can run your tests on _all_ of your local browsers via:
wct
#### WCT Tips
`wct -l chrome` will only run tests in chrome.
`wct -p` will keep the browsers alive after test runs (refresh to re-run).
`wct test/some-file.html` will test only the files you specify.