Tools: Unknown property rule warns on @property declared properties, like rootPath and importPath

[justinfagnani]

_From @coreyfarrell on April 1, 2017 4:37_

Description

Polymer builtin data binding property importPath is not recognized.

Versions & Environment

• Polymer CLI: 0.18.0-pre.15
• node: v6.10.0
• Operating System: Fedora 25

Steps to Reproduce

1. Use [[importPath]] databinding in a custom element template.
2. Set "lint": { "rules": ["polymer-2"] } in polymer.json.
3. Run polymer lint.

Results

warning [databind-with-unknown-property] - importPath is not declared or used more than once.
Adding the annotation /** @polymerElement @extends Polymer.Element */ before the class declaration of the effected element did not clear this warning.

_Copied from original issue: Polymer/polymer-cli#640_

[justinfagnani]

This is an intended warning. The polymer linter should have always warned if you don't declare a property used in a template, or use it twice in the template. It's to protect against typos in data-binding expressions.

[justinfagnani]

Oops! I just realized that importPath is a property declared on Polymer.Element. Sorry for closing prematurely.

The declaration of rootPath and importPath are declared in @jsdoc annotations, here: https://github.com/Polymer/polymer/blob/master/lib/mixins/element-mixin.html#L107

/cc @rictic

[justinfagnani]

@rictic this may be more of an analyzer bug, to read @property annotations on classes.

[coreyfarrell]

Does a work-around exist? I mean can I add an annotation to suppress this warning for the one place where I use [[importPath]]? This prevents me from using polymer lint in my build process since it causes a failure exit code.

[abdonrd]

Any news about this? I have the same issue with the rootPath.

[bashmish]

Similar issue with resolveUrl in "polymer-2-hybrid" (I guess not only).

[peterlauri]

I'm having the same issue, causing me to not use polymer lint in my build process.

[TrebuhD]

One workaround is to include importPath in your properties object, but there should be an annotation to prevent this warning.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.