doc on Listeners[] is wrong, real format is Listeners[]=request/input@ezxFormHandler::input #257
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
…@ezxFormHandler::input
|
Thanks, format changed halfway true to allow filters to be used for several events.. No one in charge pr say, but yes events/filters/signals are nice and has a big potential for allowing the kernel to be slim and let many features be optional as listeners. If async events are added to the mix as well you have nice potential for high performance by deferring certain events to later in a general way. |
andrerom
added a commit
that referenced
this pull request
Dec 16, 2011
doc on Listeners[] is wrong, real format is Listeners[]=request/input@ezxFormHandler::input
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.
real format is indicated in site.ini [Event]
I've tested successfully this format, this commit is safe
Someone knows who is in charge of ezpEvent ? nice thing for the future...