Update Examples

[chrisdrackett]

As part of this PR I updated example 1 in the following ways:

• upgrade to using babel
• upgrade deps

I've never run the examples myself and wasn't having much luck getting example 1 to run. I switched over to using babel-typescript so that our current typescript errors don't break the build. I got past that part and the page now shows up in the browser, but with errors.

At this point I feel like I might be missing steps, and think my errors probably have something to do with conflicting react versions between the base node_modules and the node_modules in example 1. (Uncaught Invariant Violation: Rendered fewer hooks than expected. This may be caused by an accidental early return statement.)

I don't have any more time right not to spend on it but figured it can't hurt to put my work so far up.

closes #67

[mweststrate]

No problem, I'll look into it!

[mweststrate]

Pushed some changes, it seems that the typescript generation wasn't really kept up to date.

• Fixed the generation of interfaces for input_objects, this seems to be a regression, as it was already fixed in generating typescript input types #36
• Made the TS types much more robust against circular types by using interfaces (per MST readme). Most probably fixes "RootStoreBase implicitly has type 'any' ..." when generating models for a Hasura schema #72, Circular dependencies between models #45
• Several other TS fixes, should also fix yarn test and yarn start fails #67
• Updated the readme instructions for examples, in the sense that the current instructions should work again :) (at least worked for me locally for example 1 and 2 again)
• Replaced webpack with Parcel in example 1, to see if it simplifies the setup. And it really does :)

Fixed the following examples:

• example 1
• example 2
• example 3
• example 4
• example 5

Ideally I would want to verify that the other examples are still working, but probably I won't have much time in the coming week, so it might be a good idea to merge this PR already after review, as it fixes quite a bunch of open issues (and makes mst-gql usable in TS again)

[chrisdrackett]

@mweststrate I'm taking a look at this now, I'll see if I can't get all the examples running!

[chrisdrackett]

ok, I fixed example 3 and updates some docs. I'll see if I can't get 4 and 5 running as well.

[chrisdrackett]

ok, I need to stop for now, but I got everything but example 4 running. If anyone else has experience with Apollo I'd love help getting it going as I've never used it!

[chrisdrackett]

I might go ahead and merge this and open a new issue to fix example 4. @elie222 thoughts?

[mweststrate]

Sounds like a plan! Op za 3 aug. 2019 23:30 schreef Chris Drackett <notifications@github.com>:

…

I might go ahead and merge this and open a new issue to fix example 4. @elie222 <https://github.com/elie222> thoughts? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#69?email_source=notifications&email_token=AAN4NBGEVZ2HATFA6WSQ7KDQCX2GRA5CNFSM4IISW7HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3PWDMY#issuecomment-517956019>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAN4NBFECRLHNXWXN3HE66LQCX2GRANCNFSM4IISW7HA> .

[elie222]

Will take a look at example 4 tomorrow. Familiar with Apollo

[chrisdrackett]

@mweststrate when using this in my own project I'm seeing a typescript error that I don't see in the examples:

Type 'IOptionalIType<IMapType<any>, [undefined]>' is not assignable to type 'string | number | boolean | Date | IAnyType'.
  Property '[$type]' is missing in type 'IOptionalIType<IMapType<any>, [undefined]>' but required in type 'IAnyType'.

any thoughts on what might be causing this?