Typescript declaration files script

[diyaayay]

This is based off of #6777 and #6972. WIP.
Maybe an AST based approach could be added to the current script. This still needs to handle a few cases, such as static methods.

Changes:

Screenshots of the change:

PR Checklist

• npm run lint passes
• Inline documentation is included / updated
• Unit tests are included / updated

[diyaayay]

I think this still needs work, the format of the output files, and cases to be handled. But, @davepagurek Do you think this would be the correct approach to bypass tsc and generate .d.ts files.

[davepagurek]

I think that's probably the best way forward, since it seemed pretty hard to get tsc to understand how we're adding to p5 classes dynamically. Looking good so far!

[davepagurek]

A more complex case you might want to try with is paletteLerp, which has an array of tuples:

p5.js/src/color/creating_reading.js

Lines 1090 to 1091 in c643b7b

	* @method paletteLerp
	* @param {[p5.Color, Number][]} colors_stops color stops to interpolate from

Ideally that out output basically back out to its original format, or possibly Array<[p5.Color, number]>

[davepagurek]

Hi @asukaminato0721, I also wanted to get your feedback on this! The approach, I think, will end up being pretty similar to p5.ts where we aren't directly running tsc on the code, but hopefully we can set this up in a way that can help us keep things up-to-date more easily.

In the p5.ts implementation, there are also some manual patches that get applied in addition to generating things directly from the docs: https://github.com/p5-types/p5.ts/tree/master/patches @diyaayay we should see if we can update this in p5 itself too if we can.

[diyaayay]

Hi @asukaminato0721, I also wanted to get your feedback on this! The approach, I think, will end up being pretty similar to p5.ts where we aren't directly running tsc on the code, but hopefully we can set this up in a way that can help us keep things up-to-date more easily.

In the p5.ts implementation, there are also some manual patches that get applied in addition to generating things directly from the docs: https://github.com/p5-types/p5.ts/tree/master/patches @diyaayay we should see if we can update this in p5 itself too if we can.

Sure, I'll look into all the patches and see how many of these are still applicable on the dev-2.0 branch.

[asukaminato0721]

Hi @asukaminato0721, I also wanted to get your feedback on this! The approach, I think, will end up being pretty similar to p5.ts where we aren't directly running tsc on the code, but hopefully we can set this up in a way that can help us keep things up-to-date more easily.

In the p5.ts implementation, there are also some manual patches that get applied in addition to generating things directly from the docs: https://github.com/p5-types/p5.ts/tree/master/patches @diyaayay we should see if we can update this in p5 itself too if we can.

This looks promise! I like it.