Skip to content
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.

Commit

Permalink
Merge branch 'hotfix/55'
Browse files Browse the repository at this point in the history
Close #55
  • Loading branch information
weierophinney committed Jul 11, 2017
2 parents 0337745 + 407a483 commit cf3900a
Show file tree
Hide file tree
Showing 4 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion doc/book/api.md
Original file line number Diff line number Diff line change
Expand Up @@ -244,7 +244,7 @@ Attach a listener to a named event triggered by an identified context, where:
### detach()

```php
detach(callable $listener, $identifer = null, $eventName = null) : void
detach(callable $listener, $identifier = null, $eventName = null) : void
```

Detach a listener, optionally from a single identifier, and optionally from a
Expand Down
2 changes: 1 addition & 1 deletion doc/book/migration/changed.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ trigger($event, $target = null, $argv = []);
triggerUntil(callable $callback, $event, $target = null, $argv = []);
```

with the following defintions:
with the following definitions:

- `$event` is a string event name.
- `$target` is a value representing the target of the event.
Expand Down
4 changes: 2 additions & 2 deletions doc/book/tutorial.md
Original file line number Diff line number Diff line change
Expand Up @@ -314,7 +314,7 @@ class LogEvents implements ListenerAggregateInterface
>
> The trait `Zend\EventManager\ListenerAggregateTrait` can be composed to help
> implement `ListenerAggregateInterface`; it defines the `$listeners` property,
> and the `detach()` logic as demostrated above.
> and the `detach()` logic as demonstrated above.
You can attach this by passing the event manager to the aggregate's `attach()`
method:
Expand Down Expand Up @@ -548,7 +548,7 @@ stored in the object, and also to ensure the listeners have the exact same
context as the calling method. But it raises an interesting problem in this
example: what name do we give the result of the method? One standard that has
emerged is the use of `__RESULT__`, as double-underscored variables are
typically reserved for the sytem.
typically reserved for the system.

Here's what the method will look like:

Expand Down
2 changes: 1 addition & 1 deletion test/EventManagerAwareTraitTest.php
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ public function testSetEventManagerWithEventIdentifier()

$object->setEventManager($eventManager);

//check that the identifer has been added.
//check that the identifier has been added.
$this->assertContains($eventIdentifier, $eventManager->getIdentifiers());

//check that the method attachDefaultListeners has been called
Expand Down

0 comments on commit cf3900a

Please sign in to comment.