Adding classname aliases to prevent conflicts #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Model\NotificationEventManager was conflicting with Entity\NotificiationEventManager when building the bootstrap cache.
This only seems to happen when building a new bootstrap cache. I suspect because in the process of building the bootstrap the Entity\NotificationEventManager was being loaded sometime before the Entity\NotificationEventListener is loaded, at which point 'using' the Model\NotificationEventManager brings it within the Entity\ namespace, causing the conflict.
Adding the alias resolves the error.