Re: [w3c/webcomponents] Using private fields and methods in template instantiation (#808)

Not a fan myself. In general, `private` in OO  means you can't access it outside of that class. Your template has to be parsed by a parser, which is outside of your class. It feels odd to me that this parser should need to access private members.

I know that Angular requires your members to not be private if you're going to use them in a template (for performance reasons, these errors only appear when running `ng serve` or `ng build` with `--prod`).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/808#issuecomment-507021469