Refactored rendering logic for nav block #33224
Closed
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
Moved rendering logic from navigation.php to the navigation block's SSR
file. This was done so that all of the rendering logic lived inside of
the block and would be subject to the project lifecycle of the block
rather than that of the navigation editor.
How has this been tested?
Activate any theme leveraging __unstableLocation on a navigation block (such as Quadrat).
Note that the navigation block still appropriately renders navigation from the class menu location.
Ensure that the experimental Gutenberg menu editor continues to work as expected.
Types of changes
Code Refactor
Checklist:
*.native.js
files for terms that need renaming or removal).