Implement filter parsing #4

New Issue

oysteikt · 2024-12-13T18:45:12+01:00

oysteikt commented

2024-12-13 18:45:12 +01:00

Filters are built up with non-regular grammar. Either we need to implement a parser with a stack of some sort, or we could use a framework like nom. Also, there are some non-documented details about filters, particularly a shorthand where you just write the tag name and value without any parenthesis.

Note that there also are some places in the protocol where the next command argument could be either a filter or something else, meaning that we probably should not consume iterators and the like before we know for sure that we expect a filter.

See:

Filters are built up with non-regular grammar. Either we need to implement a parser with a stack of some sort, or we could use a framework like `nom`. Also, there are some non-documented details about filters, particularly a shorthand where you just write the tag name and value without any parenthesis. Note that there also are some places in the protocol where the next command argument could be either a filter or something else, meaning that we probably should not consume iterators and the like before we know for sure that we expect a filter. See: - https://mpd.readthedocs.io/en/latest/protocol.html#filters - https://github.com/MusicPlayerDaemon/MPD/blob/master/src/song/Filter.cxx

oysteikt added this to the (deleted) project 2024-12-18 23:29:08 +01:00

oysteikt referenced this issue

2024-12-18 23:43:20 +01:00

Implement filter invocation #9

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Grzegorz/empidee#4