Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we standardise the approaches and have common tools to import external libraries and type declarations? #10

Closed
Happypig375 opened this issue Oct 24, 2021 · 3 comments

Comments

@Happypig375
Copy link

Happypig375 commented Oct 24, 2021

Fable for JS uses ts2fable to import from DefinitelyTyped or .d.ts source files elsewhere. It does not contain external type bindings by itself and this task is delegated to external repos such as fable-browser and fable-node.
Meanwhile, this repo states

This library will eventually contain Python (stdlib) bindings for Fable based on Python typeshed. It will also contain type binding for many other libraries as well such as Flask, MicroBit and many more.

Can we standardise the approaches and have common tools to import external libraries and type declarations?

@dbrattli
Copy link
Collaborator

This is the optional external repo containing type bindings for Fable Python

@Happypig375
Copy link
Author

But there's no automation like ts2fable, correct?

@dbrattli
Copy link
Collaborator

No, not yet. But the point is that tools like ts2fable do not produce the code you really want to use. The output can be used as a starting point for a type-binding, but the final result should be iterated and reviewed manually before making a PR to a repo like e.g this one. See also #5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants