Skip to content

Expression language: for_all hard to read and whitespace aware parser needed #2

Description

@pieterbos

consider the following expression snippet:

for_all $event in /data/events /some/other/path > $event/items/value

This is quite hard to read, plus the parser needs to be whitespace aware in order to understand wh. Xpath solved this in xpath 2 and 3 with the following syntax:

every $event in /data/events satisfies /some/other/path > $event/items/value

And

some $event in /data/events satisfies /some/other/path > $event/items/value

So, we can do:

  • use 'for_all ... in ... '. I'm not a native English speaker, but I cannot find anything that works well and is much shorter than 'for_all ... in ... the following must evaluate to true', compared to 'for_all ... in
  • use the 'every .. in ... satisfies'-syntax from xpath
  • make the parser whitespace aware

I would prefer the 'every'-syntax, but if someone has a good suggestion for what comes after for_all...

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