Socket
Socket
Sign inDemoInstall

@npm-polymer/iron-meta

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@npm-polymer/iron-meta

Useful for sharing information across a DOM tree


Version published
Maintainers
1
Created
Source

Build status

Demo and API docs

##<iron-meta>

iron-meta is a generic element you can use for sharing information across the DOM tree. It uses monostate pattern such that any instance of iron-meta has access to the shared information. You can use iron-meta to share whatever you want (or create an extension [like x-meta] for enhancements).

The iron-meta instances containing your actual data can be loaded in an import, or constructed in any way you see fit. The only requirement is that you create them before you try to access them.

Examples:

If I create an instance like this:

<iron-meta key="info" value="foo/bar"></iron-meta>

Note that value="foo/bar" is the metadata I've defined. I could define more attributes or use child nodes to define additional metadata.

Now I can access that element (and it's metadata) from any iron-meta instance via the byKey method, e.g.

meta.byKey('info');

Pure imperative form would be like:

document.createElement('iron-meta').byKey('info');

Or, in a Polymer element, you can include a meta in your template:

<iron-meta id="meta"></iron-meta>
...
this.$.meta.byKey('info');

##<iron-meta-query>

iron-meta is a generic element you can use for sharing information across the DOM tree. It uses monostate pattern such that any instance of iron-meta has access to the shared information. You can use iron-meta to share whatever you want (or create an extension [like x-meta] for enhancements).

The iron-meta instances containing your actual data can be loaded in an import, or constructed in any way you see fit. The only requirement is that you create them before you try to access them.

Examples:

If I create an instance like this:

<iron-meta key="info" value="foo/bar"></iron-meta>

Note that value="foo/bar" is the metadata I've defined. I could define more attributes or use child nodes to define additional metadata.

Now I can access that element (and it's metadata) from any iron-meta instance via the byKey method, e.g.

meta.byKey('info');

Pure imperative form would be like:

document.createElement('iron-meta').byKey('info');

Or, in a Polymer element, you can include a meta in your template:

<iron-meta id="meta"></iron-meta>
...
this.$.meta.byKey('info');

Keywords

FAQs

Package last updated on 03 Jun 2017

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc