-
|
Try adding a For example a route for the styles which is registered in a clean install of Nova without resources looks as follows:
Obviously this will clean when registering a Now I now the workaround would be to rename my resource to something else and specify the Style model manually but just using a different prefix for the routes would ensure that you would never run into this issue at all. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
This has been defined in our documentation under Reserved Resource Name: https://nova.laravel.com/docs/4.0/resources/#defining-resources |
Beta Was this translation helpful? Give feedback.
-
|
So why wouldn't you just create a prefix for the resource routes to ensure you don't get clashes? |
Beta Was this translation helpful? Give feedback.
This has been defined in our documentation under Reserved Resource Name: https://nova.laravel.com/docs/4.0/resources/#defining-resources