LocalKey to an

Context

The original Actions API design was oriented towards invoking actions from
widgets, and having those actions act in the context of the widget.
Teams have been using actions, and found several limitations in that
design that needed to be addressed:

Actions couldn’t be invoked from outside of the widget hierarchy.
Examples of this include processing a script of commands,
some undo architectures, and some controller architectures.

The mapping from shortcut key to Intent and then to
Action wasn’t always clear, since the data structures
mapped LogicalKeySet =>Intent and then
LocalKey => ActionFactory. The new mapping is still
LogicalKeySet to Intent but then it maps Type
(Intent type) to Action, which is more direct and
readable, since the type of the intent is written in the mapping.