Venelin Iliev

> @hotrush I can confirm removing the GOOGLE_CLOUD_STORAGE_API_URI from env resolved this issue for me. resolve the issue but if you use a custom domain for cloud storage? without this...

I want to use both at the same time. if I use middleware I can't access the resource/type and the other benefits I have directly in the authorizer.

first executes one, if successful executes the second as well. in the old version, I could have one in the resource and one from the routing like ->authorizer() and working....

I think it would be quite convenient for people like me to migrate to the new version. i tested with **"laravel-json-api/laravel": "^1.0"** and there are no problems with conflicts. BUT...

> @veneliniliev you need to use `laravel-json-api/laravel:^2.0` as that works with PHP 8.1 (it fixes that readonly problem). yes, but I return to the first problem. obviously, migration will not...

this is good news. if I can help with something... i'm ready :)

I hope you can find a good solution. it would be very convenient to smoothly migrate versions. I have a project with a lot of tests and I will find...

all my tests passed! I will test a little more and the installation of the new package. tnx!

@lindyhopchris I have a problem. in the old version, the order of includes was different. example: includes=relation.subrelation in v4 response: includes:[ subrelation..., relation... ], in v5 response: includes:[ relation... subrelation...,...

@lindyhopchris everything looks fine. already works on prod!