nayjest / di-hub Goto Github PK

Example: '@' means that item2 placed in outer hub.

$hub->addDefinition(new Relation('item1', '@item2', $callback));

Impl. details: SubHub should remove relations with ext. dependencies from internal hub and add corresponding relations to external hub.

Todo: Define behavior when multiple external hubs available

Example:

new ComplexRelationDefinition(
    'target_id', 
    ['source1_id', 'source2_id'],
    function(&$taget, $source1, $source2) {
        &$target = $source1 + $source2;
    }
);

CompoundDefinition is abstract class that can add multiple items to hub.

Requirements: possibility to remove CompoundDefinition from hub

Uncomment to fail tests: https://github.com/Nayjest/di-hub/blob/v0.4-dev/tests/Integration/SubSubHubTest.php#L31

Related code: https://github.com/Nayjest/di-hub/blob/v0.4-dev/src/SubHub.php#L150

Possible solution:
Support of multiple external hubs in one SubHub.

Possible flags:

1. Value::FLAG_PRIVATE
private item

Behaviour:

• $hub->has() == true
• $hub->get()/set() must throw exception

Use-case:
implementation of internal items for multi-source relation definitions, see #3

2. Value::FLAG_IMMUTABLE
Value can't be changed via relations or $hub->set()

Behaviour:
Throw exceptions when trying modify item via $hub->set() or when value is used as target in relations.

Use-cases: useful when it's prohibited to modify or replace item during app lifetime

3. Value::FLAG_NOT_INITIALIZED

Draft, not implement it, design it first. (TODO)

$hub->set() should be called at least once

1. Use 'v0.4-dev' branch
2. See https://github.com/Nayjest/di-hub/blob/v0.4-dev/tests/Integration/SubSubHubTest.php
3. Remove 'abstract' keyword to add test into test suite
4. Run tests, see errors
5. Solve issues

Case:

We have hub with $item and two dependencies: $a, $b.
Relation [a --> item] replaces $item instance (or makes $item->b not actual in any other way).

Relation [b --> item] should be always processed after calling `$hub->set('a', some_value)`.
Relation [b --> item] should use instence created in [a --> item]

If it's possible with current Di-Hub architecture, document solution.