|Number of watchers on Github||68|
|Number of open issues||1|
|Average time to close an issue||28 days|
|Average time to merge a PR||3 days|
|Open pull requests||1+|
|Closed pull requests||3+|
|Last commit||over 3 years ago|
|Repo Created||about 5 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||dart-archive|
|Do you use polymer-dart-patterns? Leave a review!|
|View polymer-dart-patterns activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
Small, useful, snippets/samples that show how to do things the Polymer way.
Port of polymer.js snippets in https://github.com/PolymerLabs/polymer-snippets.
All snippets go in
Each snippet should have its own directory. Here is a typical list of files for a snippet:
my_element.html: the HTML for
my_element.dart: the Dart code for
index.html: the entry point for the snippet. Imports
README.md: the documentation for the snippet. This should mirror the documentation in the original as much as possible.
Unless there is a compelling reason to do so, name your element
Be sure to add the snippet to the
entry_points list in
When porting a
polymer.js snippet, be sure to reference the original, and
include the commit ID. For example:
See https://help.github.com/articles/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit for details on how to get a link to the commit ID.
All snippets should follow the Dart Style Guide.
Before creating a pull request, please run the sample in Dart Editor, ensuring that it runs in both JS and Dartium without errors or warnings.
Samples using Polymer elements.