Default date format

It's not possible to replace it in your complete application, but you can replace it in your Eloquent models with a simple trait. You simply load the trait on the model you want a different date format for and you are done ;)

I have an example trait in this gist which converts Carbon to Jessenger\Date: https://gist.github.com/bobbybouwmann/c912814003883955a4c1aae9dcbb97e3

What about the packages that use Eloquent? Like Passport? Editing the package will revert the changes once the package is updated

You don't edit the file. You create a trait...

@bobbybouwmann I still don't get you. My current problem is that I can't create any tokens due to carbon throwing an invalid arguments exception. All models I have used to throw the same exception. For the models, they extend an abstract class that extends Eloquent model with the date format set. Is there any way to fix the date format in the packages without editing them?

@bobbybouwmann the expected SQL Server date format is

protected $dateFormat = 'Y-m-d H:i:s';

but what the query grammar is giving is

protected $dateFormat = 'Y-m-d H:i:s.000'

The Laravel\Passport\Token model will use the builder grammar since it directly extends Model. @JeffreyWay any way to sort this without modifying the package?

Like I said you use a trait. You clearly have no idea what a trait is: http://php.net/manual/en/language.oop5.traits.php

A trait is some kind of class that can be included in many places. So in this case if you a method in it that's the same as the extended class it will override that. So you can override the basic behaviour of the Eloquent class with that trait.

@bobbybouwmann I understand what a trait is and they help a lot with multiple inheritance. The problem is changing the packages. If I include the trait in the Laravel\Passport\Token model, I would have modified the package. When it is updated, it will revert all changes that I made thus, its always a bad idea to modify packages. The trait would work on the Models I create without any problem since I maintain them.

Aah I didn't understood that you wanted to replace the Token model in the passport package. I think you should create an issue on Github since this is a package specific problem

@bobbybouwmann exactly. The problem is with these packages that are maintained by other people. If in app.config we could set the default date format to be used across Laravel, the issue would be sorted. Thanks though.

Just create the issue and see what will happen ;) I will keep an eye on the issue once it's created ;)

@smodav have you created the issue? I'd be curious what its state is.

@AMCSI - Passport now allows the changing of the base models that are used, thus all the issues are sorted. https://laravel.com/docs/5.8/passport#overriding-default-models