Skip to content

Feedback: Comma in state is confusing #71

@ahalbert

Description

@ahalbert
/foo/ -> 
/bar/ ->, println

this surprised me because I though that if the match at the beginning of a line was false then I could just skip to the next line, but instead what I need to do is scan for a comma to see if there is another statement. I understand that the purpose of the comma is to allow anonymous states with more than one statement, but I would have a less error prone time reading if each statement had be on its own line but could start with a specific character to indicate that it was still part of the same state as the previous statement.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions