Skip to content

Commit f461844

Browse files
committed
remove extra stuff from release notes
2 parents 969bc63 + 52684bd commit f461844

File tree

8 files changed

+89
-780
lines changed

8 files changed

+89
-780
lines changed

Diff for: authorization.md

+34
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,40 @@ Gates are Closures that determine if a user is authorized to perform a given act
4848
});
4949
}
5050

51+
Gates may also be defined using a `Class@method` style callback string, like controllers:
52+
53+
/**
54+
* Register any authentication / authorization services.
55+
*
56+
* @return void
57+
*/
58+
public function boot()
59+
{
60+
$this->registerPolicies();
61+
62+
Gate::define('update-post', 'PostPolicy@update');
63+
}
64+
65+
#### Resource Gates
66+
67+
You may also define multiple Gate abilities at once using the `resource` method:
68+
69+
Gate::resource('posts', 'PostPolicy');
70+
71+
This is identical to manually defining the following Gate definitions:
72+
73+
Gate::define('posts.view', 'PostPolicy@view');
74+
Gate::define('posts.create', 'PostPolicy@create');
75+
Gate::define('posts.update', 'PostPolicy@update');
76+
Gate::define('posts.delete', 'PostPolicy@delete');
77+
78+
By default, the `view`, `create`, `update`, and `delete` abilities will be defined. You may define additional abilities by passing an array as third argument to the `resource` method. The key of the array defines the name of the ability while the value defines the method name:
79+
80+
Gate::resource('posts', 'PostPolicy', [
81+
'posts.photo' => 'updatePhoto',
82+
'posts.image' => 'updateImage',
83+
]);
84+
5185
<a name="authorizing-actions-via-gates"></a>
5286
### Authorizing Actions
5387

Diff for: billing.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -42,9 +42,9 @@ Laravel Cashier provides an expressive, fluent interface to [Stripe's](https://s
4242

4343
#### Composer
4444

45-
First, add the Cashier package for Stripe to your `composer.json` file and run the `composer update` command:
45+
First, add the Cashier package for Stripe to your dependencies:
4646

47-
"laravel/cashier": "~7.0"
47+
composer require "laravel/cashier":"~7.0"
4848

4949
#### Service Provider
5050

@@ -111,9 +111,9 @@ For many operations, the Stripe and Braintree implementations of Cashier functio
111111

112112
#### Composer
113113

114-
First, add the Cashier package for Braintree to your `composer.json` file and run the `composer update` command:
114+
First, add the Cashier package for Braintree to your dependencies:
115115

116-
"laravel/cashier-braintree": "~2.0"
116+
composer require "laravel/cashier-braintree":"~2.0"
117117

118118
#### Service Provider
119119

@@ -311,7 +311,7 @@ Alternatively, you may set a specific quantity using the `updateQuantity` method
311311

312312
$user->subscription('main')->updateQuantity(10);
313313

314-
For more information on subscription quantities, consult the [Stripe documentation](https://stripe.com/docs/guides/subscriptions#setting-quantities).
314+
For more information on subscription quantities, consult the [Stripe documentation](https://stripe.com/docs/subscriptions/quantities).
315315

316316
<a name="subscription-taxes"></a>
317317
### Subscription Taxes

Diff for: broadcasting.md

+11
Original file line numberDiff line numberDiff line change
@@ -287,7 +287,18 @@ By default, each broadcast event is placed on the default queue for the default
287287
* @var string
288288
*/
289289
public $broadcastQueue = 'your-queue-name';
290+
291+
If you want to broadcast your event using the `sync` queue instead of the default queue driver, you can implement the `ShouldBroadcastNow` interface instead of `ShouldBroadcast`:
290292

293+
<?php
294+
295+
use Illuminate\Contracts\Broadcasting\ShouldBroadcastNow;
296+
297+
class ShippingStatusUpdated implements ShouldBroadcastNow
298+
{
299+
//
300+
}
301+
291302
<a name="authorizing-channels"></a>
292303
## Authorizing Channels
293304

Diff for: csrf.md

+5-9
Original file line numberDiff line numberDiff line change
@@ -21,15 +21,9 @@ Anytime you define a HTML form in your application, you should include a hidden
2121

2222
The `VerifyCsrfToken` [middleware](/docs/{{version}}/middleware), which is included in the `web` middleware group, will automatically verify that the token in the request input matches the token stored in the session.
2323

24-
#### CSRF Tokens & Vue
24+
#### CSRF Tokens & JavaScript
2525

26-
If you are using the [Vue](https://vuejs.org) JavaScript framework without the authentication scaffolding provided by the `make:auth` Artisan command, you will need to manually define a `Laravel` JavaScript object in your primary application layout. This object specifies the CSRF token Vue should use when making requests:
27-
28-
<script>
29-
window.Laravel = {!! json_encode([
30-
'csrfToken' => csrf_token(),
31-
]) !!};
32-
</script>
26+
When building JavaScript driven applications, it is convenient to have your JavaScript HTTP library automatically attach the CSRF token to every outgoing request. By default, the `resources/assets/js/bootstrap.js` file registers the value of the `csrf-token` meta tag with the Axios HTTP library. If you are not using this library, you will need to manually configure this behavior for your application.
3327

3428
<a name="csrf-excluding-uris"></a>
3529
## Excluding URIs From CSRF Protection
@@ -71,9 +65,11 @@ Then, once you have created the `meta` tag, you can instruct a library like jQue
7165
}
7266
});
7367

68+
> {tip} By default, the `resources/assets/js/bootstrap.js` file registers the value of the `csrf-token` meta tag with the Axios HTTP library. If you are not using this library, you will need to manually configure this behavior for your application.
69+
7470
<a name="csrf-x-xsrf-token"></a>
7571
## X-XSRF-TOKEN
7672

7773
Laravel stores the current CSRF token in a `XSRF-TOKEN` cookie that is included with each response generated by the framework. You can use the cookie value to set the `X-XSRF-TOKEN` request header.
7874

79-
This cookie is primarily sent as a convenience since some JavaScript frameworks, like Angular, automatically place its value in the `X-XSRF-TOKEN` header.
75+
This cookie is primarily sent as a convenience since some JavaScript frameworks and libraries, like Angular and Axios, automatically place its value in the `X-XSRF-TOKEN` header.

Diff for: homestead.md

+14-2
Original file line numberDiff line numberDiff line change
@@ -268,6 +268,18 @@ Homestead supports several types of sites which allow you to easily run projects
268268

269269
The available site types are: `apache`, `laravel` (the default), `proxy`, `silverstripe`, `statamic`, and `symfony2`.
270270

271+
<a name="site-parameters"></a>
272+
#### Site Parameters
273+
274+
You may add additional Nginx `fastcgi_param` values to your site via the `params` site directive. For example, we'll add a `FOO` parameter with a value of `BAR`:
275+
276+
sites:
277+
- map: homestead.app
278+
to: /home/vagrant/Code/Laravel/public
279+
params:
280+
- key: FOO
281+
value: BAR
282+
271283
<a name="configuring-cron-schedules"></a>
272284
### Configuring Cron Schedules
273285

@@ -299,8 +311,8 @@ By default, the following ports are forwarded to your Homestead environment:
299311
If you wish, you may forward additional ports to the Vagrant box, as well as specify their protocol:
300312

301313
ports:
302-
- send: 93000
303-
to: 9300
314+
- send: 50000
315+
to: 5000
304316
- send: 7777
305317
to: 777
306318
protocol: udp

Diff for: mix.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ Because Laravel Mix is built on top of Webpack, it's important to understand a f
166166
background: url('../images/example.png');
167167
}
168168

169-
> {note} Absolute paths for `url()`s will be excluded from URL-rewriting. For example, `url('/images/thing.png')` or `url('http://example.com/images/thing.png')` won't be modified.
169+
> {note} Absolute paths for any given `url()` will be excluded from URL-rewriting. For example, `url('/images/thing.png')` or `url('http://example.com/images/thing.png')` won't be modified.
170170
171171
By default, Laravel Mix and Webpack will find `example.png`, copy it to your `public/images` folder, and then rewrite the `url()` within your generated stylesheet. As such, your compiled CSS will be:
172172

@@ -181,7 +181,7 @@ As useful as this feature may be, it's possible that your existing folder struct
181181
processCssUrls: false
182182
});
183183

184-
With this addition to your `webpack.mix.js` file, Mix will no longer match `url()`s or copy assets to your public directory. In other words, the compiled CSS will look just like how you originally typed it:
184+
With this addition to your `webpack.mix.js` file, Mix will no longer match any `url()` or copy assets to your public directory. In other words, the compiled CSS will look just like how you originally typed it:
185185

186186
.example {
187187
background: url("../images/thing.png");

0 commit comments

Comments
 (0)