We're updating the issue view to help you get more done. 

MassIndexer service registration should not depend on ORM services registry

Description

The current implementation of MassIndexer is registered in the ORM serviceregistry, this works fine but makes Search tightly coupled to the internal registry API, making it hard to stay compatible with a broader range of ORM versions.

Search has an alternative registry strategy which it should use to keep a sane decoupling.

Environment

None

Status

Assignee

Sanne Grinovero

Reporter

Sanne Grinovero

Labels

None

Suitable for new contributors

None

Pull Request

None

Feedback Requested

None

Fix versions

Priority

Critical