-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigation: Move the ALLOWED_BLOCKS const to a shared location #50323
Conversation
In theory, could this be filterable to allow third-party extenders to add their own blocks to Navigation blocks? |
Size Change: -14 B (0%) Total Size: 1.37 MB
ℹ️ View Unchanged
|
It could break things but that would be up to the extender to guard against. Either way I think it should be a different PR :) |
Yeah, definitely a separate PR, I was just curious if this would be the correct "thing" to filter if we ever wanted to allow that functionality. |
Not sure if we want to open that box 😅 Maybe an Related discussion #15682. |
Sorry but this appears to be a partial duplicate of #50191. Can we normalize towards that early PR? |
Closing in favour of #50191 |
What?
Creates a new shared file to store the list of ALLOWED_BLOCKS inside the Navigation block
Why?
So that they can't get out of sync.
Testing Instructions
Check that the navigation block is still limited to the blocks inside ALLOWED_BLOCKS.