John, > 1. Handling of relationships (with user defined phantom types) >
Elm does not support phantom types (to my understanding). What do you have in mind here? How can phantom types represent relationships? In regards to code gen, as I see it, the only thing needing to be generated > would be the Resource representation. > Interesting. I take it you are generating resource definitions from the Postgres schema. In my library, the resource's representation (as a type alias of a record of attributes) is the input to the code gen, the one thing that is *not* generated. > Many people argue that decoders and encoders are the pain point, but I > think with a good query builder API this pain is alleviated. I was unable > to come up with a general API myself (hence the domain specific library I > made), so I am interested in your efforts. > I'm also limiting myself, specifically to JSON API, but that doesn't make assumptions about the database. And I think one might as well generate encoders and decoders, at least if not overridden, so that the code one must write by hand (those type aliases) is as minimal as possible. > Would love to chat! I'm usually on slack + the sf meetup. > I'm in San Jose, so hopefully I'll see you there in the next few months. Please introduce yourself and remind me of this email :) -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
