From 79aa1c4699d8f5e9c5844b834cd55e933fc2c9ba Mon Sep 17 00:00:00 2001 From: Martin Kiesel Date: Wed, 19 Nov 2014 16:35:02 +0100 Subject: [PATCH 1/2] Update events.md --- events.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/events.md b/events.md index d5c1a837fd2..dc72ec6bb35 100644 --- a/events.md +++ b/events.md @@ -22,7 +22,9 @@ The Laravel `Event` class provides a simple observer implementation, allowing yo #### Firing An Event - $event = Event::fire('auth.login', array($user)); + $response = Event::fire('auth.login', array($user)); + +The `fire` method returns an array of responses that you can use to control what happens next in your application. #### Subscribing To Events With Priority @@ -47,7 +49,9 @@ Sometimes, you may wish to stop the propagation of an event to other listeners. So, you know how to register events, but you may be wondering _where_ to register them. Don't worry, this is a common question. Unfortunately, it's a hard question to answer because you can register an event almost anywhere! But, here are some tips. Again, like most other bootstrapping code, you may register events in one of your `start` files such as `app/start/global.php`. -If your `start` files are getting too crowded, you could create a separate `app/events.php` file that is included from a `start` file. This is a simple solution that keeps your event registration cleanly separated from the rest of your bootstrapping. If you prefer a class based approach, you may register your events in a [service provider](/docs/ioc#service-providers). Since none of these approaches is inherently "correct", choose an approach you feel comfortable with based on the size of your application. +If your `start` files are getting too crowded, you could create a separate `app/events.php` file that is included from a `start` file. This is a simple solution that keeps your event registration cleanly separated from the rest of your bootstrapping. + +If you prefer a class based approach, you may register your events in a [service provider](/docs/ioc#service-providers). Since none of these approaches is inherently "correct", choose an approach you feel comfortable with based on the size of your application. ## Wildcard Listeners From c72a4d0a39d8531bc4a5ebdd8d9fb4728e944dc7 Mon Sep 17 00:00:00 2001 From: Martin Kiesel Date: Wed, 19 Nov 2014 23:03:32 +0100 Subject: [PATCH 2/2] Update validation.md --- validation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/validation.md b/validation.md index f95190d0692..b252fcd4483 100644 --- a/validation.md +++ b/validation.md @@ -322,7 +322,7 @@ The field under validation must be formatted as an IP address. #### max:_value_ -The field under validation must be less than or equal to a maximum _value_. Strings, numerics, and files are evaluated in the same fashion as the `size` rule. +The field under validation must be less than or equal to a maximum _value_. Strings, numerics, and files are evaluated in the same fashion as the [`size`](#rule-size) rule. #### mimes:_foo_,_bar_,... @@ -336,7 +336,7 @@ The file under validation must have a MIME type corresponding to one of the list #### min:_value_ -The field under validation must have a minimum _value_. Strings, numerics, and files are evaluated in the same fashion as the `size` rule. +The field under validation must have a minimum _value_. Strings, numerics, and files are evaluated in the same fashion as the [`size`](#rule-size) rule. #### not_in:_foo_,_bar_,...