From f18231168b8b63298390d1e4000577e329aa18b4 Mon Sep 17 00:00:00 2001
From: abe33 <cedric.nehemie@gmail.com>
Date: Mon, 7 Dec 2015 13:41:09 +0100
Subject: [PATCH] Add a element decorator to handle creating custom elements

---
 lib/decorators/element.js | 44 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)
 create mode 100644 lib/decorators/element.js

diff --git a/lib/decorators/element.js b/lib/decorators/element.js
new file mode 100644
index 00000000..c9fa5559
--- /dev/null
+++ b/lib/decorators/element.js
@@ -0,0 +1,44 @@
+'use babel'
+
+import {registerOrUpdateElement} from 'atom-utils'
+
+/**
+ * Generates a decorator function to convert a class into a custom element
+ * through the `registerOrUpdateElement` method from `atom-utils`.
+ *
+ * The decorator will take care to return the generated element class so that
+ * you can just export it directly as demonstrated below.
+ *
+ * As supported by the `registerOrUpdateElement` method, static member will
+ * be available on the new class.
+ *
+ * **Note: As there's some limitations when modifying the prototype
+ * of a custom element, if you need to inject element callbacks (like
+ * `createdCallback`) through a mixin, the mixins should be included before
+ * converting the class as a custom element. You'll be able to achieve that by
+ * placing the `include` decorator after the `element` one as shown in the
+ * second example.**
+ *
+ * @param  {string} elementName the node name of the element to register
+ * @return {Function} the element class as returned by
+ *                    `document.registerElement`
+ * @example
+ * @element('dummy-element-name')
+ * export default class SomeClass {
+ *   // ...
+ * }
+ *
+ * @element('dummy-element-with-mixin')
+ * @include(SomeMixin)
+ * export default class SomeClass {
+ *   // ...
+ * }
+ */
+export default function element (elementName) {
+  return function (cls) {
+    let elementClass = registerOrUpdateElement(elementName, {
+      class: cls
+    })
+    return elementClass
+  }
+}