We have cases where class members are "package private" - used internally by Angular, but not part of the external api. Currently the documentation for these members is hidden, but the d.ts file contains them. We should hide them from the d.ts files as well.
We can't use Typescripts visibility markers like private for this, because we need Angular core code outside of the current class to be able to access it.
It would be great to solve this properly in Typescript, but in the meantime, we should adjust our .d.ts generation template to look for these members and not emit them during the d.ts generation process.
cc: @alexeagle, @mprobst, @rkirov
We have cases where class members are "package private" - used internally by Angular, but not part of the external api. Currently the documentation for these members is hidden, but the d.ts file contains them. We should hide them from the d.ts files as well.
We can't use Typescripts visibility markers like
privatefor this, because we need Angular core code outside of the current class to be able to access it.It would be great to solve this properly in Typescript, but in the meantime, we should adjust our .d.ts generation template to look for these members and not emit them during the d.ts generation process.
cc: @alexeagle, @mprobst, @rkirov