On Monday, October 24, 2016 at 3:46:39 PM UTC+1, Rupert Smith wrote: > > On Wednesday, October 19, 2016 at 9:54:44 AM UTC+1, Peter Damoc wrote: >> >> What options are there? >> > > The option that probably has the most traction is Swagger (now the Open > API Initiative) : > > https://openapis.org/ > > In terms of what has been discussed here, graphql or PostgREST are more > sophisticated than Swagger, but Swagger may have relevance if its following > grows. That said, the news section in the open API initiaive is > dissapointingly empty beyond the initial announcement of the initiative: > > https://openapis.org/news > > I would find a json-schema -> Elm decoders/encoders/records converter > useful and the ability to generate the relevant Http boilerplate needed to > call endpoints defined in Swagger. It would be nice if you could pick up a > Swagger definition and create an Elm client module to work with that API > with next to no effort. >
There are some blog posts, so perhaps things are progressing after all: https://openapis.org/news-faq/blog -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
