-
Notifications
You must be signed in to change notification settings - Fork 301
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
Additional fixes for Redux #191
Additional fixes for Redux #191
Conversation
…ted modules interface definitions; include original Typescript files from which the interfaces were generated; improve documentation and include version numbering.
Nice work, thank you! The only thing I have some doubts is adding the |
On 11 June 2016 at 10:24, Alfonso Garcia-Caro [email protected]
Not sure I see the point unless the generator is driven by the .d.ts |
Here's the rationale for including the .d.ts file -- the .fs interface declarations files are not simply autogenerated from the Typescript. They are initially generated, and then modified by hand. Including the original .ts file makes it possible to trace back what by-hand modifications needed to be made to the .fs file. This should make it easier to upgrade the interface declarations to later versions when new .d.ts files come out. I was not aware of typings. I'll try working that in instead. |
Just reference a link to where the d.ts comes from and what version, you can trawl the diff at any time in the future. |
You're absolutely right, @psfblair, as the imports are manually edited it's important to track the diffs between the I have added a typings.json file to the repo and installed the typings corresponding to the currently imported definitions. You should be able to recover them by installing typings globally: You'll see that the |
Are you waiting for anything from me on this? I have typings, but I'm not entirely sure where the registry urls in typings.json came from. The only one that needs to be added is for react-router. As I mentioned on a different issue, I'm afraid I'm not going to be able to carry this forward. I haven't successfully got Redux working, and there's some type problem with the way components are wired to the Redux state that I haven't been able to figure out. It's conceivable that this has to do with the interface definitions, but it seems more likely that it has to do with something going on under the hood. |
I was waiting for your thoughts on whether the |
I had removed the .d.ts files from the branch, but I did put a link into the READMEs which I can remove if you like. The main thing is that the react-router typing isn't part of the typings.json. |
Perfect, thanks for that! I just merged the PR and then removed |
The brunch skeleton for Fable/Redux is on GitHub here: https://github.com/psfblair/fable_redux_skeleton -- however, it's not entirely ready yet (partly because issue #190 is blocking).