Named argument usage

[nanaya]

The documentation states:

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

But then the examples on the very same page use named arguments on laravel methods.

Can I assume all the examples with named arguments on the docs to be stable? Like here, here, here, and here to list a few. Is there a more specific guidelines on which ones can use named arguments safely? Or should I ignore the examples and use them without named arguments?

[Tamas-hi]

That is a good question, and I would also like to know. Basically what I am asking is that changed name arguments will be present in the migration guide or not.

[shaedrich]

Good question indeed. This is bugging me ever since I encountered that statement in the docs as people are constantly using named arguments in their PRs, so their changes will potentially be subject to the explained changes in the future, which could cause problems.