Skip to content

Expression language: Whitespace aware parser required in rules language for assertion separation #1

Description

@pieterbos

The current rules language requires a whitespace aware parser in two places. This issue is about the separation between assertions. Say you have the following rules syntax:

/path/to/value/one = /path/to/value/two 
/path/to/value/three = /path/to/value/four

Without a whitespace-aware parser, it's impossible to detect the beginning and end of the second path reference: is it /path/to/value/two and /path/to/value/three? or /path and /path/to/value/two/path/to/value/three? Or /path/to/value /two/path/to/value/three

I would propose a ';' as separation between assertions. This solves this problem and it quite easy to type. Also it allows you to write statements over multiple lines. But more solutions than this one are possible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions