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
We need to crank up the use of jsdoc and then we can use typescript to generate the typings.
The first thing what we can do is to make it mandatory to write correct jsdoc for new features.
Then we should integrate the typescript typings as jsdoc into our javascript code.
When all typings are migrated to javascript, we could generate the typings directly from the jsdoc and should not break the typings.
It is still necessary to use tsd to ensure that the typings are implemented right.
This would solve...
Currently typings have to written by hand.
The implementation should look like...
We need to crank up the use of jsdoc and then we can use typescript to generate the typings.
The first thing what we can do is to make it mandatory to write correct jsdoc for new features.
Then we should integrate the typescript typings as jsdoc into our javascript code.
When all typings are migrated to javascript, we could generate the typings directly from the jsdoc and should not break the typings.
It is still necessary to use tsd to ensure that the typings are implemented right.
I have also considered...
N.A.
Additional context
I created a PR #3579 as a possible solution.
If we consider this as good feature, I would look if we can transform iteratively.
Also we should consider to strip the jsdoc and all the comments when we build for node to ensure that we dont bloat the final file.
The text was updated successfully, but these errors were encountered: