Find parslet to be really useful? Or just found a bug that is really ruining the day for you? Please contribute! Find the code on github.
Join us on IRC in #parslet on irc.freenode.net.
Discussion and patches (or the odd cry for ‘Help! How can I parse X?’) should
go to our mailing list at
email@example.com. Just write a
short message to that address and librelist will
subscribe you. NNTP/web interface can be had through
Log in to github and open a bug ticket here. Please be sure to include the version of parslet and Ruby; maybe you can even provide some code that exhibits the bug?
And of course if you provide a properly tested patch, you’ll be our hero and get a place in the space below for lifetime.
Thanks for all the fish — Contributions
- Raphaël Simon (raphael) for a nice contextual error reporter!
- Dan Freeman (dfreeman) for allowing rules to be inherited!
- Rory O’Kane (roryokane) for a careful code review!
- Zach Moazeni (zmoazeni) for his work on Unicode performance.
- rogerbraun (rogerbraun) for being my unicode tester.
- meh (meh) for taking a real close look.
- John Mettraux (jmettraux) for the really nice JSON example and for pushing parslet beyond its limits.
- Josep M. Bach (txus) for minding the small things that make a big difference.
- Matthew Draper (matthewd) for bothering with my broken CSS.
- Hal Brodigan (postmodern) for solving our email parsing needs!
- R. Konstantin Haase (rhk) for rspec matchers that help stamp out, eliminate and abolish redundancy.
- Florian Hanke (floere) has given a lot of very inspiring input for parslet. His questions have been key to rounding off the corners and making the library as aesthetic as it is. And just look at the logo.
- Kaspar Schiess (absurd.li) for being brave enough to actually add another parser library to a field that’s already bursting at the seams.