Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

psmail's avatar

4.3 rumours

I thoughts I'd start capturing the snippets I am gleaming about Laravel 4.3, which I think according to the release schedule is due out in Nov.

So far I have come across two things and I thought I'd put the feelers out to see what else we know about the upcoming release.

Request based validation.

From Refresh Arkansas talk.

// routes.php

class StoreCharacterRequest extends FormRequest {
    public function rules() {
        return ['name' => 'required|unique:characters'];
    }
    public function authorize() {
        return true;
    }
}

Route::post('character/store', function(StoreCharacterRequest $request))
{
    // ...
}

New default directory structure

From Laravel podcast.

  • I don't have the details, but I imagine it will be much like the structure outlined by Taylor's book
  • Backwardly compatible - so we won't need to change existing directory structures
0 likes
7 replies
JeffreyWay's avatar

Request objects will change your workflow dramatically. Laracon EU isn't too far away. :)

psmail's avatar

Thanks, JW - I figured 4.3 would not be released until Nov, in line with the Symphony cycle. And I am keen to get onto a standardised validation approach, which I think is coming ... hence I'm just a bit eager.

JeffreyWay's avatar

It won't be released until November, yes, but I'll be covering what's new in great detail before the end of the month.

3 likes
dantreacy's avatar

@JeffreyWay Any chance with large changes like that affecting workflow that you'd consider going "back" and refactoring some of the larger LC projects/series such as Larabook, to give folks some real world idea on how to implement these changes into older projects.

mrterryh's avatar

Looking at the directory structure here, I'm really looking forward to it.

1 like
thepsion5's avatar

Request objects will change your workflow dramatically. Laracon EU isn't too far away. :)

I bet we can find a decent way to translate a request object directly to a command, man would would be great! Reminds me a lot of the Action-Domain-Reponder pattern, which I quite like and have been experimenting with on some smaller projects.

Please or to participate in this conversation.