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
I’d like to use this issue to discuss the generation work.
One thought I have is that the generated content will most likely need manual updates afterward. There has been an idea to use the APIs listed at https://developer.mozilla.org/en-US/docs/Web/API. However, right now, the generator consolidates everything into a single file. It may be beneficial to manually split things up after the generation process is complete.
The text was updated successfully, but these errors were encountered:
It's likely that some of the definitions will have to live in the same file because of recursiveness. In that case though, the main definition can live in a general file (imagine type htmlElement = {...}), but we can still have a file for HtmlElement.res:
It might be possible to generate some bindings via microsoft/TypeScript-DOM-lib-generator.
In my fork, I've started exploring how we can generate ReScript instead of TypeScript.
It's still early to report any substantial progress, but here’s what I have so far:
I’d like to use this issue to discuss the generation work.
One thought I have is that the generated content will most likely need manual updates afterward. There has been an idea to use the APIs listed at https://developer.mozilla.org/en-US/docs/Web/API. However, right now, the generator consolidates everything into a single file. It may be beneficial to manually split things up after the generation process is complete.
The text was updated successfully, but these errors were encountered: