Is your feature request related to a problem? Please describe.
This custom command in login.commands.js file:
generates this definition in customCommands.d.ts file:
So the original JSDoc comment is simply repeated above the respective command definition in .d.ts file. However the parameter types for that command are parsed to be any.
IntelliSense then uses the generated any types for parameters
Describe the solution you'd like
Using the parameter types specified in the original JSDoc comment for the custom command type definition would be, I think, much more helpful. This means we could simply auto-generate the customCommands.d.ts file after adding/editing any custom commands and wouldn't have to correct the types again and again.
Is your feature request related to a problem? Please describe.
This custom command in
login.commands.jsfile:generates this definition in
customCommands.d.tsfile:So the original JSDoc comment is simply repeated above the respective command definition in .d.ts file. However the parameter types for that command are parsed to be any.
IntelliSense then uses the generated any types for parameters
Describe the solution you'd like
Using the parameter types specified in the original JSDoc comment for the custom command type definition would be, I think, much more helpful. This means we could simply auto-generate the customCommands.d.ts file after adding/editing any custom commands and wouldn't have to correct the types again and again.