Conversation

Aug 9, 2018

I really dislike the trend that several Rust web frameworks are following of using annotations on functions to define routes. Being able to quickly see which routes are available on an application in one place is extremely useful, as is using a function for multiple routes

Brendan Zabarauskas

@brendanzab

Aug 9, 2018

Big fan of Haskell's Servant library's way of dealing with this, where the API is a type. Wish we had some alternative in Rust land for this: haskell-servant.readthedocs.io/en/stable/inde

jkachmar

@jkachmar

Aug 9, 2018

I hope Rust gets a Yesod-like before it gets something along the lines of Servant tbh. Servant is cool, and I like it a lot, but the difficulty curve is ROUGH and I still get tripped up regularly. Type safe routes would be awesome either way though.

Replying to

and

Interesting, what are the common paper cuts for you with Servant?

11:46 PM · Aug 9, 2018Twitter Web Client

Replying to

and

Until 0.14 added a Generic module for deriving routes from records (rather than :<|>) the type errors for large APIs could get monstrous. I haven’t tested the new stuff thoroughly, but errors are supposedly much better.

jkachmar

@jkachmar

Aug 10, 2018

Outside the happy path (JSON APIs with JWT or Basic Auth) you’ll probably have to roll some stuff on your own. Because type level programming is still relatively heavy stuff, extending the library can get a little hairy depending on what you’re doing.

Show replies