What would you love to see in Laravel 5.1?

I think that should have something to make easy package publishing something at updates.

I've an package that publish some Assets, but everytime I update this package, the user must run php artisan vendor:publish.

I'll love if some feature like php artisan vendor:autopublish --package=Vendor/PackageName that always autopublish package assets...

A sound way / instructions of how to develop packages, now that workbench is out of the picture.

Agreed and acl, or a least a package like cashier and socialite

@Kryptonit3 They are, and he's saying: ACL to be an official package like these 2.

@EliasSoares, you could just advise your users to put php artisan vendor:publish --provider="Your\Provider in the composer.json post-update-cmd scripts. then they won't have to run the command every time.

An official acl package would be very cool.

But the improvements in 5.1 are already awesome :)

+1 on ACL

The problem with ACL is, there isn't one way to implement it. Different apps haves different needs when it comes to ACL, so I will confidently say we won't see ACL in Laravel itself, or as an "official" package.

The problem with ACL is, there isn't one way to implement it

This is the point. It would be some kind of "standardization" of a classic user / role /permission system. if you need more complex implementation it is up to you. There is many way to validate data too but validator / rules / form request kind of standardized the way you do it. When you know laravel and look to another project you see a form request, a unique rule, you know what's going on.

Right know there is about as many implementation of ACL as dev wanting to implements an ACL system.

And according to the number of threads about ACL on this forum (even basic implementation) there would be huge benefits.

@pmall But you just have to look at projects like Entrust and Lock and see how complex they are that there isn’t one single way to implement ACL. There are just too many variables. It’s not something that can be tweaked with a config file and fit every one’s needs like a queue or database adapter can be. ACL is a topic unto itself.

A basic ACL approach could be provided nevertheless. And it can be handled as with HTML and FORM that it's not included directly by default but has to be 'loaded'.

I hope to see one day Carbon instantiated through a contract. This will allow us to use its localized versions without extra overhead, caused by creating a localized instances from vanilla ones.

Remember the method (post or other) with the intented path when middleware catch a request.

Currently, only get method works

Remember the method (post or other) with the intented path when middleware catch a request.

Intended path is for redirection. It is a nonsense to redirect to a post request.

Is the release still dated for May?

Symfony 2.7 has to come out first before 5.1 is released.

I would love to see Laravel Eloquent Query Language like DQL in doctrine.

The problem with ACL is, there isn't one way to implement it.

Before Laravel we also could say "The problem with PHP framework is, there isn't one way to implement it". I think Taylor can find some way to federate all needs.

Before Laravel we also could say "The problem with PHP framework is, there isn't one way to implement it".

Not the same thing at all. A framework is a starting point. ACL is an implementation.

Some way to easy setup a socket.io server and have php and js play nice together :)

More consistent helpers would be nice. We have route get/post, route any, route pattern is absent.

@sijdesign You’re going to love the broadcasting component coming in Laravel 5.1: https://laracasts.com/lessons/broadcasting-events-in-laravel-5-1

Is the node server file for socket.io going to come default with 5.1? @martinbean

Probably not. That was just a quick example.

Is there any way i can see what is coming to 5.1 :D?

Everything You Need To Know About Laravel 5.1

@martinbean I agree that ACL is an implementation not a framework. However Laravel already uses an authentication implementation, so I don't think it is outside the scope to have roles and permissions added to Auth. If one needs to use ACL, using an external package often means you need to use their authentication system as well, rendering Auth superfluous.

As someone who relies heavily on what I learn here at Laracasts, and as someone who needs to use ACL in most of my projects, I wish I could make use of Auth in my work since Jeffrey does such a great job explaining how to use it.

That said, I don't expect anything like this for 5.1 but hopefully it would be something put on the roadmap.

ACL would be great.

Also want linked in as a provider of socialite.

A more powerful Blade. For instance there were times when I needed to use continue in a loop but that was not possible.

ACL would be great indeed