@Snapey you do not need this, you can pass data throughout the component

I wish when I create the model he get the fillable from database when I give him PHP artisan make:model post --table posts and get $table name

Model data localization out of the box

1. Create Model(s) folder in app and place User model there
2. I method to update the modified time on the $scheduler mutexPath return storage_path('framework'.DIRECTORY_SEPARATOR.'schedule-'.sha1($this->expression.$this->command));

we run really long cron jobs, and sometimes it crashes. i can write another cronjob to delete the schedule files in /storage/framework/schedule* but we dont know if its still running. if we had a method to to be able to update the modify time from within my code this would be solved

@Mevrael can you share your uploadable trait ? I am really interested

Make laravel 4.2 compatible with PHP 7 and name it Laravel 5.3.

• Built-in Oauth
• Built in transient tokens (like Spark)

@imJohnBon I'm using current DatabaseSeeder with condition:

if (!App::environment('production')) { } else { }

Nothing special, but works like a charm :)

@wells and @foxted did you tried "lucadegasperi/oauth2-server-laravel" ? It is not something you always need in application, so it should not be a part of out of the box configuration.

ACL scaffolding with database

Definitely would like to se some more localization support. When you just need to do localization for pages, it's fine, but for models, it gets to be messy. We've cobbled something together for our current project, but I would love to see the full might of Laravel turned to the problem.

Would love to see better handling of failed migrations. Having to go back into the db and manually delete gets old.

Wonder if it's possible to do some version of have-many-through for many-to-many relationships.

1. I second "Create Model(s) folder in app and place User model there"

2. Spark needs to be able to implement trials where a credit card is required up front to be verified and stored by Stripe ... there are so many requests for that in the wild

Easy way to modularise parts of an app including hooking in migrations and routes for each module. (I'm aware there's probably a few packages to do this and probably a way to do this using composer)

Some front end components such as List View/Grid View would be cool to spin up some quick systems.

(Note: these ideas have been taken from Yii, probably some of the only things prevent my work from switching)

I'm from the Netherlands and we build quite some websites for clients that operate in multiple countries. Some countries (like Belgium) already have 2 official languages. Implementing this in laravel is a bit of a pain. So:

• standard localisation of model fields
• better localisation of the app with for example a gettext implementation

Migrate the database by diffing model definitions with the actual database table, like Doctrine's Schema Tool. The current approach gets a bit unwieldy when there are lots of small changes, and I keep having to refer to the actual database to check my current schema structure.

Taylor, we dont see any diferrense between register() and boot() functions in ServiceProvider(s). So - in 5.3 we must get first -> load all register() method for existing ServiceProviders (besides deferred) and only then call boot() methods.

It's so strange to have two methods making the same things and calling the same time.

Please, look here: link to example

• CRUD Generator with support for customization of the stubs. There are third-party packages attempting to do this but they aren't well supported.
• Add to the above: Tests, API, Validation -- All these generated when it's generating controllers, views, routes and other things for the CRUD. So if we have a Post model and we fire this command. It'll create tests, views to read, create, update & delete (With Validation), Controller, API (Optional Flag) and ofc the routes itself.
• Migrations Generator from Database (Like someone already requested +1).

Native Event Sourcing support (Event Store).

@foxted agree with @arekpietrzyk oauth is just one of many authentication method and having it baked within Laravel will make it limited. Yes its an important authentication used by many application but "used by many but not used by all" doesn't imply that it needs to be implemented within the framework. Hence why application packages exists.

More about Laravel 5 CRUD generation (scaffolding) would be very nice to have :)

More JSON field query helpers for Eloquent! :)

ie) https://twitter.com/stauffermatt/status/741373051174932480

@Mevrael, not to start a discussion but to use 'Mail::sendConfirmationToUser($user)', I would create a seperate mailer class. It's been covered on Laracasts for sure. The way Laravel's mailer works is fine. The callbacks are easy to use. And if you don't want to use a template, you can always use 'Mail::raw()'. Good luck!

How about the ability to use dot notation in the get method of the Collection class?

@Kostik There is a difference between boot and register. See: https://laravel.com/docs/master/providers#the-register-method for more details.

When you're logic depends on a service bound to the ioc container, you should place it in the boot method. Placing it in the register method would add the risk of the service not yet being bound to the ioc because it's service provider is loaded after the one with your logic. That explains why the first foreach loop only calls 'register()' and the the second 'boot()' :).

@Kostik & @Juukie - it would be nice if they were declared in the order they are called as well!

Add explicit publish() setup method to service providers, so we don't have to execute code in boot which only needs to be called during installation.

-Scaffolding for Roles and Permission like make:auth -Built in packages for SMS like twilio

I'd like a simplified files structure like the file structure of rails simple and effective.

Y'all know you can just add an app/Models directory and put your models in there, right?

The app folder is PSR-4 namespaced, meaning that as long as you follow the naming structure (StudlyCaps folders and class names), Composer will automatically load those classes for you.

-Ability to turn off blade caching completely for dev env's

-Show blade file names when an error is thrown instead of the hash