Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for configurable wrapped handlers #49

Merged
merged 2 commits into from
Feb 18, 2016
Merged

Add support for configurable wrapped handlers #49

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aed1eb1
Add support for configurable wrapped handlers
michaelmoussa Feb 17, 2016
af78161
Update README with new reserved keys
michaelmoussa Feb 17, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update README with new reserved keys
  • Loading branch information
@michaelmoussa
michaelmoussa committed Feb 17, 2016
commit af781617757eb5604292d52ff03a4e6529f65c05
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,8 @@ If some parameters are not present in the constructor, they will be treated as e
- `class` (optional): classname of the handler you would like to use
- `formatter` (optional): formatter identifier that you have defined
- `processors` (optional): array of processor identifiers that you have defined
- `handlers` (optional): array of handler identifiers that you have defined
- `handler` (optional): single handler identifier that you have defined

Other parameters will be interpreted as constructor parameters for that Handler class and passed in when the handler object is instantiated by the Cascade config loader.<br />
If some parameters are not present in the constructor, they will be interpreted as extra parameters and Cascade will try to interpret them should they match any custom handler functions that are able to use them. (see [Extra Parameters](#user-content-extra-parameters-other-than-constructors) section below)
Expand Down