Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1)

Unified Diff: polymer_1.0.4/bower_components/iron-signals/README.md

Issue 1205703007: Add polymer 1.0 to npm_modules (Closed) Base URL: https://chromium.googlesource.com/infra/third_party/npm_modules.git@master
Patch Set: Renamed folder to 1.0.4 Created 5 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: polymer_1.0.4/bower_components/iron-signals/README.md
diff --git a/polymer_1.0.4/bower_components/iron-signals/README.md b/polymer_1.0.4/bower_components/iron-signals/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..ff62a2d83465fcd528a542c4c79a72598f13b6fc
--- /dev/null
+++ b/polymer_1.0.4/bower_components/iron-signals/README.md
@@ -0,0 +1,26 @@
+iron-signals
+============
+
+`iron-signals` provides basic publish-subscribe functionality.
+
+Note: avoid using `iron-signals` whenever you can use
+a controller (parent element) to mediate communication
+instead.
+
+To send a signal, fire a custom event of type `iron-signal`, with
+a detail object containing `name` and `data` fields.
+
+```javascript
+this.fire('iron-signal', {name: 'hello', data: null});
+```
+
+To receive a signal, listen for `iron-signal-<name>` event on a
+`iron-signals` element.
+
+```html
+<iron-signals on-iron-signal-hello="helloSignal">
+```
+
+You can fire a signal event from anywhere, and all
+`iron-signals` elements will receive the event, regardless
+of where they are in DOM.
« no previous file with comments | « polymer_1.0.4/bower_components/iron-signals/.gitignore ('k') | polymer_1.0.4/bower_components/iron-signals/bower.json » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698