Added ability to customize the listener priorities #384
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ic value in the config
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
by setting a numeric value in the config.
In the current implementation it is not possible to adjust the default/hardcoded listener priorities anyhow. Thus, as an example, the loggable listener creates a LogEntry before the blameable and/or timestample behaviors adjusts the respective fields.
If one wants to store those fields in the LogEntry as well there was no chance.
With this PR one set a numeric value to the configured behaviors in addition to just set it to
true. This does not only allow to define custom priorities for those listeners which are registered without any, it also allows to override the hardcoded values of theStofDoctrineExtensionsExtensionclass.