
This check ensures that all Polymer properties are also declared as class members, which in turn is useful for the - ongoing work to roll out the 'declare' keyword. - future Polymer -> Lit migrations Also updating lit-property-accessor and polymer-property-declare checks to mention the class name in reported errors, as well as to use a more accurate selector for the 'properties' object in their implementation. In order to enable the new check also fixing a couple remaining violations that were not fixed in previous CLs, and adding `enable_type_aware_eslint_checks=false` to CrOS Settings configuration until all violations are fixed (tracked at crbug.com/406583052). Bug: 406463492,406583052 Change-Id: I00eb8028ac7bfde6db93676c16f4e5ad2e60a0bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6176307 Reviewed-by: Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/main@{#1439142}
Chromium
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead,
follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.