Skip to content

Parsing "/" #43

Open
Open
@bigs

Description

@bigs

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:

lit "" *> lit "" *> end

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions