Skip to content

Remove wp.element; embrace ReactΒ #876

Closed

Description

We already have a lot of React-specific code in various places in the editor, so the wp.element.createElement abstraction has been more confusing than helpful for a while now. It seems to me like we are trying to pretend that we're not tied to using React, but this is a giant, untested assumption. I see two possible ways forward here:

  1. Test this assumption and solidify our abstraction by proving that it is possible to switch to a different view rendering engine.
  2. Drop the assumption and call our use of React by the name React.

Per recent discussion in core Slack, WP core has basically decided to adopt React. We are now well-positioned to prefer option (2) and remove as much of wp.element as possible.

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

Metadata

Assignees

No one assigned

    Labels

    FrameworkIssues related to broader framework topics, especially as it relates to javascript[Type] TaskIssues or PRs that have been broken down into an individual action to take

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions