Skip to content

Clean up code for move to v12 #299

@rachel-fenichel

Description

@rachel-fenichel

Organize action code to prepare for moving to v12 and moving code into core.

My goal with this organization is to identify which parts of the code have significant dependencies and which operate as standalone. Many actions only need a few pieces of information: a canCurrentlyEdit function, a workspace, a getState function, and a cursor on which to act.

The Navigation class currently has implementations of a lot of callbacks. Several can be encapsulated in their respective actions, while the remainder give us information about missing APIs. The Navigation and NavigationController classes also add handlers, change listeners, and monkeypatches that will become unnecessary as their implementations are moved into core.

Several actions clearly can move into separate files, including both the shortcut/context menu and the actual implementation of the action:

Other actions may need to be deleted wholesale (#286, #264, and #295).

There is already a PR open to remove the markedNode field from navigator.ts (#273)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions