Problem/Motivation
There is no real point for us to limit Project Browser blocks by whether the relevant source is enabled or not. In fact, it makes it harder to control the derived Canvas components' visibility, if the blocks themselves may or may not exist.
Proposed resolution
(AI generated) The BlockDeriver class is being updated to derive block plugins for all available source plugins, not just those that are enabled. This change ensures that blocks are exposed for every possible source, regardless of their enabled state, by using all source plugin definitions instead of filtering for enabled ones.
Issue fork project_browser-3552012
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
penyaskitoLGTM, checked with Phéna in Vienna sprints
Comment #4
chrisfromredfinI like what we're doing here, but I don't think we should show a block if it's not enabled. I think handling it by having the block show no output if it's disabled is more The Right Thing™ here.
(Have discussed w/ Adam in the Contrib Room)
Comment #5
phenaproximaComment #7
tim.plunkettMerged, thanks!
Comment #9
phenaproximaThis should probably be backported. I suspect it will be a clean cherry-pick.
Comment #11
chrisfromredfinThis cherry-picked clean to 2.0.x and was pushed.