It's like you read my mind... I very consciously designed this in such a way that it would be possible to do this. More to the point: I think it would be possible to use web-routes-quasi to create a RESTful API and then auto-generate the basic API documentation. I'd like to eventually figure out a way to support GET and POST parameters as well for this.<div>
<br></div><div>Anyway, for the basic [String] methods, I can add support for it in the future; I'd rather wait until we have the rest of web-routes settled down first.</div><div><br></div><div>(Of course, a patch is always welcome.)</div>
<div><br></div><div>Michael<br><br><div class="gmail_quote">On Tue, Apr 6, 2010 at 1:16 AM, Peter Robinson <span dir="ltr"><<a href="mailto:thaldyron@gmail.com">thaldyron@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Again, nice work! :) The web-routes-quasi package makes writing routes quite<br>
enjoyable. One thing that I was wondering about is, is it possible to<br>
get the list of supported methods (as [String]) for a given url?<br>
<font color="#888888"><br>
Peter<br>
</font><div><div></div><div class="h5"><br>
<br>
On 4 April 2010 20:34, Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>> wrote:<br>
> ... and now that's done :-). You can use whatever methods you want now, and<br>
> it also solves the annoying issue when importing both Web.Routes.Quasi and<br>
> Network.Wai.<br>
> Michael<br>
><br>
> On Sun, Apr 4, 2010 at 10:16 AM, Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>><br>
> wrote:<br>
>><br>
>> Because I want to eventually get rid of the Method datatype entirely and<br>
>> allow arbitrary methods ;).<br>
>> Michael<br>
>><br>
>> On Sat, Apr 3, 2010 at 9:53 AM, Peter Robinson <<a href="mailto:thaldyron@gmail.com">thaldyron@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> Nice work!<br>
>>><br>
>>> Is there a specific reason for excluding HEAD and OPTIONS?<br>
>>><br>
>>> Peter<br>
>>><br>
>>> On 3 April 2010 00:51, Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>> wrote:<br>
>>> > web-routes-quasi is now at the point where it can be used for sites,<br>
>>> > and I'd<br>
>>> > love to hear some feedback. I've put together a little sample that<br>
>>> > demonstrates how you can use quasi-quoting and define your routes,<br>
>>> > embed<br>
>>> > subsites and serve the resulting application via WAI. (My example uses<br>
>>> > WAI,<br>
>>> > but the package itself is not tied to WAI.)<br>
>>> > The code is on github[1]; the main function for the blog is in blog.hs<br>
>>> > (with<br>
>>> > the lowercase b). I believe this just depends on Jeremy's web-routes<br>
>>> > package, wai and wai-extra.<br>
>>> > Note that I did not use web-routes-wai; I think there are some problems<br>
>>> > in<br>
>>> > there for breaking up the pathinfo, and I didn't have time to dig<br>
>>> > through<br>
>>> > it. Also, this package currently ignores entirely the defaultPage<br>
>>> > component<br>
>>> > of Site, though if there is desire support can be added for it.<br>
>>> > One minor bug is that you can't have an alternate GET, POST, PUT or<br>
>>> > DELETE<br>
>>> > constructor imported; hopefully that will get cleaned up.<br>
>>> > Any comments and suggestions are welcome! My goal is to port Yesod over<br>
>>> > to<br>
>>> > this as soon as the web-routes set of packages are released, so if<br>
>>> > you're<br>
>>> > interested in Yesod, you should be interested in this too ;).<br>
>>> > Michael<br>
>>> > [1] <a href="http://github.com/snoyberg/web-routes-quasi" target="_blank">http://github.com/snoyberg/web-routes-quasi</a><br>
>>> > _______________________________________________<br>
>>> > web-devel mailing list<br>
>>> > <a href="mailto:web-devel@haskell.org">web-devel@haskell.org</a><br>
>>> > <a href="http://www.haskell.org/mailman/listinfo/web-devel" target="_blank">http://www.haskell.org/mailman/listinfo/web-devel</a><br>
>>> ><br>
>>> ><br>
>><br>
><br>
><br>
</div></div></blockquote></div><br></div>