refactor: derive Ruby action namespaces from Rust catalog

2026-10-09 17:07:29 +02:00
parent dbafaf6266
commit 18dc8cc155
5 changed files with 67 additions and 34 deletions
@@ -26,6 +26,7 @@ A named frontend ability required by a feature for compatibility, not a permissi
 ## Configuration interfaces

 - Prefer typed objects for editor-owned actions, modes, and other closed sets. Expose new core binding targets through `config.core` rather than requiring command-name strings.
+- `src/editor.rs`'s `CORE_ACTIONS` is authoritative for core action names and eligibility. Ruby action methods and nested namespaces are generated from its startup catalog; add or rename actions there rather than maintaining a second Ruby list.
 - Use strings for open-ended identifiers: language IDs, paths, and external plugin command names. Interactive Ex command names remain textual.
 - Ruby action/mode objects provide validation during configuration evaluation and discoverable members, not compile-time enum safety.