Closed (fixed)
Project:
Drupal core
Version:
8.8.x-dev
Component:
plugin system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Aug 2018 at 10:54 UTC
Updated:
22 Jul 2019 at 08:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
andypostComment #3
xanoThanks!
For reference: this mirrors
ExecutableManagerInterface::execute().Comment #4
alexpottI find this all very confusing looking at \Drupal\Core\Condition\ConditionManager::execute() since that calls ->evaluate() and there are no usages of ExecutableException in core.
I'm tempted to mark this as a duplicate of #2385427: Add a ConditionManagerInterface because that issue should really be updating \Drupal\Core\Condition\ConditionPluginBase::setExecutableManager() to typehint on the new ConditionManagerInterface.
Comment #5
andyposthm, good idea - could be incorporated into related
But actually
execute()should allow throwing exceptionComment #6
xanoIn #2385427-29: Add a ConditionManagerInterface you observed changing the type hint in
BlockFormwould be a BC break. That class is explicitly marked internal, and if I understand our BC policy correctly, plugin classes are internal as well. Could you help me understand the difference between both cases? :)Comment #8
ghost of drupal pastHere's the absolute minimum for this issue, together with #3065586: ConditionManager::execute() implementation doesn't conform to the interface it would make it much easier to understand the code flow of the condition plugins.
Comment #9
ghost of drupal pastComment #10
alexpott#8 looks great - if someone could rtbc it then I'd commit it.
Comment #11
bircherComment #12
alexpottCommitted and pushed 7daf1e6988 to 8.8.x and 82731b8283 to 8.7.x. Thanks!
Backported as this is a docs only change.