Skip to content
This repository has been archived by the owner on Sep 7, 2022. It is now read-only.

Need declarative lazy imports for views, otherwise they look like undefined custom elements #3

Open
rictic opened this issue Mar 4, 2017 · 0 comments

Comments

@rictic
Copy link

rictic commented Mar 4, 2017

i.e. in polymer-1-app/src/my-app.html there's

          <basic-view name="basic-view"></basic-view>
          <content-view name="content-view"></content-view>
          <name-view name="name-view"></name-view>
          <shadowdom-v0-styles-view name="shadowdom-v0-styles-view"></shadowdom-v0-styles-view>
          <polymer-dom-view name="polymer-dom-view"></polymer-dom-view>
          <not-found-view name="not-found-view"></not-found-view>

But these elements look like they're undefined, and the linter says so. Solutions in descending order of niceness:

  • Add lazy imports to the source, make the analyzer/linter understand them
  • Teach the linter to ignore a warning for a range of source
  • Use the ignore clause of polymer.json to ignore undefined element warnings entirely.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant