One thing I would like to see (maybe in Laravel 6) is just using regular path syntax for views.

The whole dot syntax thing has always felt to me like it's just trying to look object oriented for the sake of it. It's using a JS style in PHP, with no actual benefits, just making it feel more complex than it should be, when we're simply referencing files.

Using /path/to/absolute or ../path/to/relative would make it obvious, reduce one level of abstraction, and make refactoring easier.

@davestewart I believe you can already do that... View::make('post.create') is the same as View::make('post/create'), I believe.

I guess it just does a string replace leaving any slashes in there :P

I ended up writing a Blade directive that lets me write relative paths, but when I was learning Laravel, it just felt like yet another thing that was different, when this could actually have been made very straightforward. A path is a path; it doesn't need a DSL.

Is Taylor reading any of this?

@EmilMoe in the begining he replayd to some, but now not anymore for a while, so i guess he isn't? :( ill send him a twitter to ask ;)

A user voice like system would probably an easier way to organise it with so much response :-)

I wish the make:auth create a profile settings also. Like

change password change user profile. change name and others.

that's pretty need I think for every project.

thank you @TaylorOtwell :)

We could help a lot of people on this forum if the crash stack trace showed the content of the request object, or at least the URL being called.

@Snapey maybe he should bring whoops back by default like back in the Laravel 4 days.

I have a feature request for laravel 5.3 I think if we allow the developer to extend the Auth Events classes it would be great because currently if the /Illimunate/Auth/Event/* is raised and I want to broadcast the Login event to the client i have no way to do this.

It simply cannot be done.

It would be nice if we could allow for extending this class yes i know it could raise some issues with the passed it constructor parameters..

But what do you think?

@Khudadad and others concerning the pagination thing really. In another post I demonstrated double pagination one for outter foreach another for the inner foreach Loop. Seriously it's a framework sometimes we have to roll up our sleeves and actually brace yourself sit down if you're standing Code something for ourselves.

UUID ids by default for Eloquent models

To not give these folks everything they want on a silver platter, rather encourage them to roll up their sleeves put on a good pot of coffee and actually program some things for themselves, to actually think some hard things through.

@lundz Create a custom event class and use that one instead of the default auth.login event.

Model folder and namespaces for it by default

That is already there it's called the users model.

@Ricardo I will be pleased to help you with the translations.

May be a config writer which will write the config values in the file ?

May be a config writer which will write the config values in the file ?

Not a bad idea, but I'm not sure if that should be a core feature. Sounds like a weekend project though :)

Model Events In Polymorphic Relations To Work.

do you maybe know when Laravel 5.3 come :( maybe @TaylorOtwell

Coming Soon™

@TaylorOtwell Firebase Support

Hello dears can you tell me here i have 3 table like as user table ,test table ,demo table . And user table field look like as user_id , name ,title etc. And test table look like as test_id ,title , user_id etc. and demo like as id ,user_id etc. i want to edit the data from test or demo table then here user_id should be in dropdown and show user_id like as 1,2,3,4,5, according to user entry in user_id field.please tell me how i do it.please tell me procedure for view ,controller,model relation for this .Please gave me same suggestion here.

@kumarmann this is the wrong topic, you'll have to make an own topic at:

https://laracasts.com/discuss/conversations/create

and please add some information there in what you allready tried ;)

Bart

"Many through Many-to-Many" relationships. like https://github.com/jarektkaczyk/Eloquent-triple-pivot .

Would love an admin panel built in with laravel. A simple but powerful one, would complete Laravel as framework.

Hello, i would like to easily set dynamic connections, for example the username and password introduced by the client, and not the one in the .env file, to avoid setting connection like this:

Config::set("database.connections.yourCustomConfig", [
    "host" => "1.2.3.4",
    "database" => "differentDBName",
    "username" => "user",
    "password" => "password"
]);

and avoid instancing this in all Models.