Remove connection from config for EventSubscribers #248
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.
Describe your change
In service configuration, I removed the
connectionattribute for the eventSubscriber. As far as I understand, if you have multiple connections, they will all be used but this should be tested more in-depth.I'm still unsure if this should be considered breaking from a SEMVER stand point
What problem is this fixing?
If your symfony doesn't have a connection called
default, it would break.