Elm 0.18 Support

[carleryd]

https://github.com/elm-lang/elm-platform/blob/master/upgrade-docs/0.18.md

[TimPerry]

+1 and update on this?

[TimPerry]

+1 and update on this?

[jahewson]

Yep, after much delay I'm working on this now. Having to rewrite the decoder codegen as it relies heavily on a custom infix operator. Should have something this week, fingers crossed.

[jahewson]

Yep, after much delay I'm working on this now. Having to rewrite the decoder codegen as it relies heavily on a custom infix operator. Should have something this week, fingers crossed.

[Bellk17]

@jahweson my fork is 0.18 compliant, though using a different GraphQl.elm file.

[Bellk17]

@jahweson my fork is 0.18 compliant, though using a different GraphQl.elm file.

[TimPerry]

@Bellk17 Any change you could do a PR?

[TimPerry]

@Bellk17 Any change you could do a PR?

[Bellk17]

@TimPerry I'll look into it tonight. I've made a number of changes on my fork to utilize this on a build server, so need to make sure no breaking changes.

[Bellk17]

@TimPerry I'll look into it tonight. I've made a number of changes on my fork to utilize this on a build server, so need to make sure no breaking changes.

[maticzav]

Any progress with this?

[maticzav]

Any progress with this?

[Gregoirevda]

+1 any update?

[Gregoirevda]

+1 any update?

[nicu-chiciuc]

It seems like the last commit was made a year ago. Is the project abandoned?

[nicu-chiciuc]

It seems like the last commit was made a year ago. Is the project abandoned?

[nickdima]

This one seems more active: https://github.com/jamesmacaulay/elm-graphql

[nickdima]

This one seems more active: https://github.com/jamesmacaulay/elm-graphql

[dillonkearns]

Hello @jahewson, I recently published a library called Graphqelm that I think achieves similar goals to this one, and has support for Elm 0.18. It actually takes the approach of generating functions for the entire schema which guarantee that you only build valid, type-safe queries. I recommend that anybody on this thread check it out! Here's a live Ellie demo.

I believe that with graphqelm, the technique of generating code for specific queries is obsolete (though perhaps you might disagree, or there is a use case I am missing). I'd be curious to hear everyone's thoughts on this.

[dillonkearns]

Hello @jahewson, I recently published a library called Graphqelm that I think achieves similar goals to this one, and has support for Elm 0.18. It actually takes the approach of generating functions for the entire schema which guarantee that you only build valid, type-safe queries. I recommend that anybody on this thread check it out! Here's a live Ellie demo.

I believe that with graphqelm, the technique of generating code for specific queries is obsolete (though perhaps you might disagree, or there is a use case I am missing). I'd be curious to hear everyone's thoughts on this.

[Gregoirevda]

Will check that out!

[Gregoirevda]

Will check that out!

[daniel-kun]

IMHO it sounds reasonable to generate the whole scheme (except when it might be gigantic). Will definitely try it out when I want to access a GraphQL API from Elm again. Thanks!

[daniel-kun]

IMHO it sounds reasonable to generate the whole scheme (except when it might be gigantic). Will definitely try it out when I want to access a GraphQL API from Elm again. Thanks!

[dillonkearns]

@daniel-kun I agree. I've been using the Github API as an example. It generates a total of 308 files, but it doesn't seem to be an issue. It's in the examples/src/Github.elm file in the repo.

[dillonkearns]

@daniel-kun I agree. I've been using the Github API as an example. It generates a total of 308 files, but it doesn't seem to be an issue. It's in the examples/src/Github.elm file in the repo.

[dillonkearns]

And another nice thing is that it gives you a clear separation between the generated code and your code, so you can freely edit your code without worrying about breaking something that was auto-generated. So having lots of files isn't necessarily an issue unless it slows down compile times or increases bundle sizes too much. That hasn't been an issue with the Github example, and Elm 0.19 is going to improve dead code elimination and some compile performance issues I believe.

[dillonkearns]

And another nice thing is that it gives you a clear separation between the generated code and your code, so you can freely edit your code without worrying about breaking something that was auto-generated. So having lots of files isn't necessarily an issue unless it slows down compile times or increases bundle sizes too much. That hasn't been an issue with the Github example, and Elm 0.19 is going to improve dead code elimination and some compile performance issues I believe.