Standalone ContentRepository.Core !

[bwaidelich]

• Get rid of ObjectManagerInterface in NodeType and NodeTypeManager
• Replace \Neos\Flow\Utility\Algorithms::generateUUID() in ID-ValueObjects
• Remove/rewrite Behat test traits!?
• Make unit tests extend \PHPUnit\Framework\TestCase instead of \Neos\Flow\Tests\UnitTestCase
• Get rid of Doctrine DBAL (v2) dependency (ContentRepository.Core: Get rid of Doctrine DBAL (v2) dependency #4989)
• SQLite support
• Expose projection DBAL Schema (Expose projection DBAL Schema #4991)
• Remove neos/eventstore-doctrineadapter dependency (no hard requirement)

- [ ] Improve NodeTypeManager API (#4228) Postponed to 9.1 or later – this can be done in a bridge layer

[bwaidelich]

NodeType and NodeTypeManager adjustments are related to #4228 but maybe we can already fix the Flow dependency so we are not blocked by the "rewrite"

[skurfuerst]

@nezaniel is working on this I guess :) or at least he has :)

[nezaniel]

#4455 should take care of the test suite dependencies

[mhsdesign]

Hi what is the status on this? I think we are mostly done with this right?

[mhsdesign]

I think it got an answer to it in https://github.com/skurfuerst/standalone-content-repository/tree/main ;)

We apparently still use Flows Algorithms https://github.com/skurfuerst/standalone-content-repository/blob/040d38f93950ca8fb028609c2ec03ca116ceb568/src/Workaround/FlowUtilityAlgorithms.php#L20 but that should be easy to adjust ^^

Also we must always declare 'Neos.ContentRepository:Root' as nodetype manually, maybe thats the only nodetype the manager should always know about?

https://github.com/skurfuerst/standalone-content-repository/blob/040d38f93950ca8fb028609c2ec03ca116ceb568/NodeTypes.yaml#L3C1-L3C30

[skurfuerst]

@mhsdesign yeah I am thinking along the same lines :):)

[mhsdesign]

Okay it seems our logic in here is still valid:

https://github.com/neos/flow-development-collection/blob/e60dab42b10b09a0a23fbe463c40562b10f2baeb/Neos.Flow/Classes/Utility/Algorithms.php#L37-L44

Ramsey\Uuid will not use by its own uuid_create, only if the feature is enabled (new FeatureSet(enablePecl: true)):

The question now is where to place this logic and if the core should have an utility and a dependency on ramsey/uuid?

All leftover usages:

• neos-development-collection/Neos.ContentGraph.DoctrineDbalAdapter/src/Domain/Projection/NodeRelationAnchorPoint.php

  Line 33 in 3fbf9fd

  return new self(Algorithms::generateUUID());

  (and also in the postgres adapter)

• neos-development-collection/Neos.ContentGraph.DoctrineDbalAdapter/Tests/Behavior/Features/Bootstrap/ProjectionIntegrityViolationDetectionTrait.php

  Line 239 in 087a0a6

  ? Algorithms::generateUUID()

[mhsdesign]

Update it seems we already have and utility which is already used for example for NodeAggregateId::create

See

Neos\ContentRepository\Core\SharedModel\Id\UuidFactory::create

neos-development-collection/Neos.ContentRepository.Core/Classes/SharedModel/Id/UuidFactory.php

Line 26 in 93aae71

public static function create(): string

That was introduced lately with #4251 and we could use it again

[bwaidelich]

I had closed this, but there are still some open tasks in order to make this thing work nicely