Skip to content

Protected template properties seems not to be the norme in angular. #924

Open
@ice-blaze

Description

@ice-blaze

Hello,

I was reviewing the TypeScript style guide and noticed that it recommends using protected for template properties:
https://google.github.io/styleguide/tsguide.html#properties-used-outside-of-class-lexical-scope

However, in practice, I rarely see this used in the documentations. Not in the Angular documentation, nor in Angular Material documentation.

Given that this rule doesn't seem to be followed in most real-world Angular codebases, would it make sense to consider removing this recommendation or just say "prefer public" instead? That would likely be the least disruptive change with minimal impact on existing projects.

Thank you for your feedback!

Metadata

Metadata

Assignees

No one assigned

    Labels

    lang:tsThe TypeScript language

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions