iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/aio/content/errors/NG8002.md
George Kalpakas fb58a2bd54 fix(docs-infra): use relative URLs for internal links on error pages (#40881) 
Previously, some of the links on the error pages had URLs prefixed with
`https://angular.io/`. This caused them to be treated as external URLs,
which had the following downsides:
- Links would always point to `angular.io` instead of the same version
  as the error page (e.g. `next.angular.io` or `v11.angular.io`).
- Dgeni would not be able to check that the URLs are valid (i.e. point
  to existing pages).
- An external link icon would incorrectly be shown next to the links on
  `angular.io`.

This commit fixes the links to use relative URLs.

PR Close #40881
2021-02-19 09:14:59 -08:00

781 B
Raw Blame History

@name Invalid Attribute @category compiler @videoUrl https://www.youtube.com/embed/wfLkB3RsSJM @shortDescription Unknown attribute or input

@description An attribute or property cannot be resolved during compilation.

This error arises when attempting to bind to a property that does not exist. Any property binding must correspond to either:

  • A native property on the HTML element, or
  • An @Input() property of a component or directive applied to the element.

The runtime error for this is NG0304: '${tagName}' is not a known element: …’.

@debugging Look at documentation for the specific binding syntax used. This is usually a typo or incorrect import. There may also be a missing direction with property selector ‘name’ or missing input.