first of all: thanks
a few small things:
I plan to prepare a release candidate for 2.3.1 soon. In order to be included in the issue report, the issue needs to specify the fixVersion. You can also assign yourself to the issue.
The getter for the boolean value misses the match context. This is hardly ever useful for this action, but I had already problems with some rules because I did not set it in other langauge elements. It is used to allow feature matches as agruments for the action, like MARKTABLE(..., SomeAnnotation.booleanFeature, ...)
It would not break compatibility if we make the argument optional:
MARKTABLE(TypeExpression, NumberExpression, TableExpression
StringExpression, NumberExpression, BooleanExpression?)?
(,StringExpression = NumberExpression)+)
What are the use cases if the user cannot configure it using the language?