-
-
Notifications
You must be signed in to change notification settings - Fork 909
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
Proposal: enhance JSDoc deprecate parameter description #976
Comments
Should we include that also in our api docs page? |
I think that would be a great idea. I don't use the API docs TBH so I didn't realize they could be in need of this feature as well. |
Yeah, I also think this would be a great idea. It would definitely improve the docs. |
Currently, we provide this information via the |
Yeah, I think it would be more clear if we moved the information to the |
If it generates a clickable link for the docs, sure go for it. |
Do you mean in the docs? Because currently there is no link in the JSDoc in my IDE :/ |
I'm referring to the api docs website: |
Here an image, as the link posted above by @ST-DDT will get stale some day |
Repeating my message here from: #1067 (comment)
|
This has been resolved by #1067. |
Clear and concise description of the problem
As a developer using faker I want to see some intel about a deprecated method in intellisense. This could help me to figure out what I should use instead without waiting for a log that tells me.
Suggested solution
Add meaningful documentation to JSDocs
deprecated
parameter.Like:
This would result in a more excellent information box resulting and in a better developer experience by not only telling me that a method is deprecated but telling me what I should do instead.
Like:
Alternative
Don't do anything
Additional context
rxjs is doing the same for their operators (just ONE reference)
The text was updated successfully, but these errors were encountered: