Fable: How do you keep Fable imports up-to-date?

[forki]

Is tehre a (fake) script that keeps the fable imports up-to-date?
Is there a chance to add react-native and things like react-native-* (like react-native-camera)?

[Krzysztof-Cieslak]

1. Running npm update updates scripts to latest version (respecting restrictions specified in package.json)
2. I'll PR react-native soon

[alfonsogarciacaro]

To be honest, my initial hope was that import packages were community maintained :wink: (As the TypeScript declaration files actually are). Probably I'll move them soon from Fable's repo as they add a lot of maintenance overhead (checking correctness of the declaration file, keeping them in sync with API updates, etc...). @mastoj suggested to have each import in its own repo once a Fable Github organisation is created, or maybe we can try to emulate DefinitelyTyped. I'm open to suggestions 😄

As react-native bindings have been mentioned, I'm adding a reference to issue #228.

[forki]

So I guess my question is: given there is a tool that can convert typescript definitions to fable, why can't we automate this to do it over everything in definitelytyped?

[alfonsogarciacaro]

Because unfortunately the parser is not perfect and most of the times manual tweaks are needed :disappointed: FunScript actually managed to parse all the declarations in DefinitelyTyped but it was in the early stages of TypeScript when the type system was much, much simpler.

Now TypeScript AST is very complex and poorly documented (and it may change a lot in the new versions). The code of the ts2fable parser is quite messy and full of hacks. I tried to use TypeScript type checker to make things more systematic but failed miserably.

[forki]

Ok thanks for clarification. It's what I assumed ;-)

On Jul 26, 2016 6:20 PM, "Alfonso Garcia-Caro" [email protected]
wrote:

Because unfortunately the parser is not perfect and most of the times
manual tweaks are needed 😞 FunScript actually managed to parse all the
declarations in DefinitelyTyped but it was in the early stages of
TypeScript when the type system was much, much simpler.

Now TypeScript AST is very complex and poorly documented (and it may
change a lot in the new versions). The code of the ts2fable parser is
quite messy and full of hacks. I tried to use TypeScript type checker
https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API#using-the-type-checker
to make things more systematic but failed miserably.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Fable/issues/281#issuecomment-235321884,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNLwIh_KjU35tyfIQoFK8AY8uyA2Iks5qZjO_gaJpZM4JU4y0
.

[mastoj]

I definitely think that the way fable grows justifies for a separate fable org. This will give:

• More fine grained control, not everyone need to have access to the core stuff when just working with an import
• More focus of what should be in core.
• Easier for others to see how to create their own import. We could even give them a minimum template for creating a new import or whatnot.

But that hasn't so much to do with the typescript stuff I guess :)

[MangelMaxime]

I like the idea to have one repo by import. Because, for me it's better to maintain them and this don't create a mess of commits when we modify another import.

[alfonsogarciacaro]

Yeah, we should move to our own organisation soon. For that we still need the logo (#183). We wanted to hire the designer of Suave's logo but unfortunately she's not available so now we're thinking to try 99designs, but if someone else have any other idea, please shoot :gun:

[forki]

concrete example: where would we put https://github.com/Krzysztof-Cieslak/fable-react_native-demo/blob/Picker/src/Fable.Import.ReactNativeImageCropPicker.fs ?

[alfonsogarciacaro]

I guess that would go in a fable-import-react-native repo within the Fable organisation (together with package.json and README.md files for publishing in npm).

[alfonsogarciacaro]

Closing the issue as we already have #183 to track the creating of own GH organization.