You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @davidbielik, I agree with you though I suspect we will take no action here. The only docstrings with [Deprecated] are the ones that you have already noted in #1575 should be removed from the library, so likely that is how we will resolve this.
Is your feature request related to a problem? Please describe.
I noticed the comments on API fields prefix
[deprecated]
, for example:stripe-node/types/2022-08-01/Checkout/Sessions.d.ts
Line 1727 in db94c29
This makes it hard to miss when looking in VScode at what's deprecated
Describe the solution you'd like
If you add
@deprecated
to the jsdoc comment:Then the property will show a strike-through in the editor which should make it more obvious to developers when using deprecated properties/methods.
Before
After
It also makes it easier when referencing properties (for example, I added
@deprecated
in the definitions):Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: