bazzline / php_component_requirement Goto Github PK

shutdown should be injected into item and should be triggerd even only on one item

@tworzenieweb is this still needed?

Else I would put it in archived mode.

We try to implement requirement items or a whole requirement.

Possible solution:

• provide public function "disable" in requirement
  • how to handle locking (if requirement is locked already?)
• provide interface "CanBeDisabled" with method "disable" that can be implemented in the requirement, collection or item

Refactor shutdown part to a more generic configuration object.

Default return value, when shutdown/disable is triggerd, for isMet has to be configurable.