Non-Eloquent models

[jk100magnys]

Problem with Non-eloquent models.
I have 4 Eloquent Resource type and 2 Non-Eloquent.
For the dev purpose Im using Laradock and in that dev environment all 6 resources works fine.
But, when I deployed that code to the other server = 4 Eloquent Resources works fine but 2 non-eloquent doesnt work at all.

I've checked 10 times

• git pull - the same files
• the same DB
• the same composer.lock (many times remove vendor folder and install again)
• the same OS
• Classes is Visible (dd shows me Entities and them works)
• routes is ok

Anyway I see the error
{ "message": "No adapter for resource type: Food", "exception": "CloudCreativity\\LaravelJsonApi\\Exceptions\\RuntimeException", "file": "/var/www/******/vendor/cloudcreativity/laravel-json-api/src/Store/Store.php", "line": 341, "trace": [

What I could forget or what maybe as a problem?

Here is the code of
config - https://pastebin.com/C09uuLTS
adapter - https://pastebin.com/k8AMuc9A
schema - https://pastebin.com/YKHqvrFw

[lindyhopchris]

Hi,

If it's working in dev but not on your deployment, might be something to do with your deployment. As it can't find the food adapter, you probably want to check the class loading / composer autoloader to ensure that the class exists.

[jk100magnys]

I've checked autoloader and composer many times.
I've tried to debug and I see that Resolver know just about Eloquent resources from the config.

If I change E-Adapters in the config - Resolver see that changes. If I change NonE-Adapters in the config - Resolver just ignore it.

And as you can see the paths to the classes in config looks the same.
Maybe you have any thoughts?

[lindyhopchris]

So if it's working on dev but not in production, without any doubt this is something to do with your setup or deployment. It's almost impossible for me to help you with it via a Github issue, you'll need to debug yourself.

The only thing that does occur to me is sometimes depending on the OS, file name detections can or cannot be case-sensitive. Check that the filenames are correctly camel-cased for your classes.

There's no difference in the resolver in detecting classes whether they are Eloquent or non-Eloquent, so there won't be a problem with the resolver. We also have multiple production applications that have a mixture of Eloquent and non-Eloquent resources and we have no problems with resolving adapters etc.

[jk100magnys]

Ok, thank you.

[raphcadiz]

@jk100magnys how did you fix this, we have the same issue on order-items resource