When I changed value of laravel-resources.models.namespace then I expects that when I will write php artisan resources:create Test this will create model Test in right namespace. But this doesn't work.

Example
I had changed the configuration on App\Models after that I ran php artisan resources:create Test.

After that the model still is generated in /app directory but with namespace App\Models

Not work with laravel 7

When running the command "php artisan resources:create Article"
On this level below, when I press enter it throws the error, The "-s" option does not exist.
Should I create the seeder for Article? (yes/no) [yes]:

I don't know whether that is the intended behaviour or not but probably it seems like an error to me.
But thanks for this great package probably I am going to make a simple article and a youtube video on how to use this package it really comes in handy.

Hello ! I just downloaded your package and I think it's great ! It really increases productivity, I only wish I discovered it sooner.

There's one thing I'm wondering though, maybe a silly thing. Why not use validate() method in the controller instead of request -> all() ?

Thanks again for that great package.

Lumen V 6.3.3
While i'm creating php artisan resources:create Post
On
Should I create the seeder for Post?
The "-f" option does not exist.

There are a lot of breaking changes from L7 to L8 like:

• factories are now class-based;
• the route system has changed;
• the new App\Models folder (this was already supported);

To keep support to L7 and add support to L8 a new release of this package must be made.

The new LaravelResources v.2.0 should be implemented with full support for L8

People that keep working with L7 should be able to pull the LaravelResources v.1.7 version

• Collections
• Resources
• Controllers
• Factories
• Migrations
• Models
• Policies
• Form Requests
• Routes
• Seeders

/composer.json has been updated
Running composer update tiagomichaelsousa/laravelresources
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- tiagomichaelsousa/laravelresources[v1.0, ..., v1.3] require illuminate/support ~5|~6 -> found illuminate/support[v5.0.0, ..., v5.8.36, v6.0.0, ..., v6.20.44] but these were not loaded, likely because it conflicts with another require.
- tiagomichaelsousa/laravelresources[v1.4, ..., v1.7] require illuminate/support ^7.0 -> found illuminate/support[v7.0.0, ..., v7.30.6] but these were not loaded, likely because it conflicts with another require.
- tiagomichaelsousa/laravelresources[v1.8, v2.0] require illuminate/support ^7.0|^8.0 -> found illuminate/support[v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
- tiagomichaelsousa/laravelresources v2.0.1 requires illuminate/support ^7.0|^8.0|^9.0 -> found illuminate/support[v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.7] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires tiagomichaelsousa/laravelresources * -> satisfiable by tiagomichaelsousa/laravelresources[v1.0, ..., v1.8, v2.0, v2.0.1].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require tiagomichaelsousa/laravelresources:*" to figure out if any version is installable, or "composer require tiagomichaelsousa/laravelresources:^2.1" if you know which you need.