-
Notifications
You must be signed in to change notification settings - Fork 792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using @internal on @Prop()s to exclude from doc generation can cause build errors #2440
Comments
We want to encourage public APIS to have docs, what's the use case for non wanting the api documented but still exposed? |
When creating a component library that has components with interact and use other components internally, we don't always want consumers interacting with certain props and events. Especially if those props and events are used only internally. So this provides an easy and benign way for library authors to exclude things from the docs generation without disturbing the build. I noticed another person asked about this as well -- #1849 The suggestion to use the |
Does this sound reasonable @manucorporat ? |
Stencil version:
I'm submitting a:
[ ] bug report
[x ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://stencil-worldwide.herokuapp.com/ or https://forum.ionicframework.com/
Current behavior:
Tagging
@internal
on@Prop()
variables could cause build errors since it removes the types from TypeScript compilation.Expected behavior:
Exclude
@Prop()
variables from doc generation without causing build errorsSteps to reproduce:
Add
@internal
to@Prop()
variables used by other components in a library will cause like this:In the above example
list-line
useslist-line-truncation
directly and the build fails sincecheckChanges
is tagged@internal
to avoid docs generationOther information:
The text was updated successfully, but these errors were encountered: