feat(compiler): Automatically add @default JSDoc to @Prop() declarations #6264
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the current behavior?
Currently, Stencil does not automatically add
@default
JSDoc to@Prop()
declarations, even when a default value is present in the component's property definition. Developers have to manually add this JSDoc.Closes: 6139
What is the new behavior?
Stencil will now automatically add
@default 'value'
to the JSDoc of a@Prop()
when a default value is detected for that property and no@default
JSDoc is already present. This improves developer quality of life by reducing redundancy and making component APIs clearer.Documentation
No new documentation is required, as this is an automatic behavior change.
Does this introduce a breaking change?
[ ] Yes
[x] No
Testing
Unit tests have been added to
src/compiler/types/tests/generate-prop-types.spec.ts
to verify the new behavior, including cases where a default value is present and where@default
JSDoc is already manually set. All tests are passing.Other information
This feature is similar to how Stencil automatically adds
@readonly
when a@Prop()
only has a getter method.