Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Local Rules #46

Open
JulienCochuyt opened this issue Jul 26, 2024 · 0 comments
Open

Local Rules #46

JulienCochuyt opened this issue Jul 26, 2024 · 0 comments

Comments

@JulienCochuyt
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant