hey all,
i've noticed a little oddity when writing my route parser... i've gotten into the practice of using end to explicitly terminate my routes (probably wroth adding notes to this effect in the docs (happy to help). anywho, end proves to be essential in stopping a "root" route parser (i.e. /) from matching everything. in order to get it to properly match, however, i had to write a parser like so:
which i found to be particularly odd, since i don't need it in routes that are further populated, i.e.
lit "" *> lit "foo" *> end
will properly match /foo
is this expected behavior? if not, is this something we should look at?
hey all,
i've noticed a little oddity when writing my route parser... i've gotten into the practice of using
endto explicitly terminate my routes (probably wroth adding notes to this effect in the docs (happy to help). anywho,endproves to be essential in stopping a "root" route parser (i.e./) from matching everything. in order to get it to properly match, however, i had to write a parser like so:which i found to be particularly odd, since i don't need it in routes that are further populated, i.e.
will properly match
/foois this expected behavior? if not, is this something we should look at?