Skip to content

Commit

Permalink
[9.x] Named arguments are covered by Laravel's backwards compatibilit…
Browse files Browse the repository at this point in the history
…y guidelines (laravel#7604)

* Adds named arguments to list of exceptions

* Update releases.md

Co-authored-by: Taylor Otwell <taylor@laravel.com>
  • Loading branch information
nunomaduro and taylorotwell authored Jan 20, 2022
1 parent 030bf08 commit 260b5d1
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,11 @@ Laravel and its other first-party packages follow [Semantic Versioning](https://

When referencing the Laravel framework or its components from your application or package, you should always use a version constraint such as `^9.0`, since major releases of Laravel do include breaking changes. However, we strive to always ensure you may update to a new major release in one day or less.

<a name="named-arguments"></a>
#### Named Arguments

[Named arguments](https://www.php.net/manual/en/functions.arguments.php#functions.named-arguments) are not covered by Laravel's backwards compatibility guidelines. We may choose to rename function arguments when necessary in order to improve the Laravel codebase. Therefore, using named arguments when calling Laravel methods should be done cautiously and with the understanding that the parameter names may change in the future.

<a name="support-policy"></a>
## Support Policy

Expand Down

0 comments on commit 260b5d1

Please sign in to comment.