Local Rules

[JulienCochuyt]

Currently, rules that have the multiple property can be matched multiple times but there is no easy way to target a specific result within the collection of their results. Hence, they are mostly used for quick navigation or control mutation.
A rule search can be restricted to a given parent context area, but its gesture triggers the action globally. Hence, such a rule with the multiple property will always see its first result targeted by the triggered action.

When a table presents buttons to act on individual lines, or when a page presents a series of forms - or tiles - each with buttons to act on individual elements group, we rely on programmatic extension to redeem a suitable UX.

The upcoming support for SubModules (PR #37) offers a workaround, but which is overkill in many simple situations.

Proposal:
Such rules could be set to target their triggered actions only within the parent context containing the caret.
This could be either the default for rules searched within a parent context that has the multiple property, and/or be configurable through a new property on the rule itself.

[JulienCochuyt]

It has finally been decided to set this new "local" scope at gesture level.
Upcoming PR.