You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just started looking at Grape. It strikes me as an extremely clean framework built on rack (and rack-mount for routing), and therefore may be good to look at for this code reading.
Rack-mount itself is interesting too. It mentions it ...supports Rack’s X-Cascade convention to continue trying routes if the response returns pass. But I don't see that documented anywhere, for instance in the interface spec nor in Rack::Cascade where I'd expect it. Anyone know where to look for info on this, is it a convention only rack-mount uses or is it used more widely?
The text was updated successfully, but these errors were encountered:
@ericgj I used to a quick look Grape as well, and I impressed about good quality codes, specs, and its simplicity API as well.
Anyone know where to look for info on this, is it a convention only rack-mount uses or is it used more widely?
I can't find it as well, but there is a short introduction section of Sinatra: Up and Running on pg 78-82 that talks about Middleware Chain, Cascade, and Rack::Mount.
I just started looking at Grape. It strikes me as an extremely clean framework built on rack (and rack-mount for routing), and therefore may be good to look at for this code reading.
Rack-mount itself is interesting too. It mentions it ...supports Rack’s
X-Cascade
convention to continue trying routes if the response returnspass
. But I don't see that documented anywhere, for instance in the interface spec nor inRack::Cascade
where I'd expect it. Anyone know where to look for info on this, is it a convention only rack-mount uses or is it used more widely?The text was updated successfully, but these errors were encountered: