Migrate post editor feature preferences to the interface package #34154
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
talldan
added
[Type] Enhancement
18 tasks
|
Size Change: +127 B (0%) Total Size: 1.04 MB
ℹ️ View Unchanged
|
7 tasks
talldan
force-pushed
the
migrate/post-editor-feature-preferences-to-interface-package
branch
from
ccf602c to
82d0bb0
Compare
7 tasks
talldan
deleted the
migrate/post-editor-feature-preferences-to-interface-package
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Partly addresses #31965. Related to #31965 and #34135.
Migrates post editor feature preferences over to the interface package.
Here there was a choice of deprecating the post editor's APIs for features, but this keeps them as backwards compatibility is pretty easy to maintain. Any selectors and actions call through to the interface store's implementation.
How has this been tested?
Types of changes
New feature (non-breaking change which adds functionality)
Checklist:
*.native.jsfiles for terms that need renaming or removal).