[11.x] Adds conditional to routes

[Boorinio]

This pull request introduces the Conditionable trait to the Laravel Route class, allowing developers to add conditional logic when defining routes. Consider the following:

Route::middleware('shop')
    ->domain('{shop}.domain.com')
    ->when(App::isProduction(), function ($route) {
        $route->whereIn('shop', app(ShopService::class)->getShopSlugs());   
    });

No Breaking Changes

This addition does not alter any existing functionality of the Route class. The Conditionable trait is introduced as an optional feature that will only be applied when explicitly used by developers. Existing routes will continue to work as expected without any modifications.

P.S. tests included.

Thanks for your time

[Boorinio]

@taylorotwell Thank you, much appreciated!!

[Eyad-Bereh]

Can you please explain how will this feature be useful? Any specific use cases you were thinking of?

[edalzell]

Can you please explain how will this feature be useful? Any specific use cases you were thinking of?

In my case I have a route that's only used in testing, this is perfect for that.

[Eyad-Bereh]

Can you please explain how will this feature be useful? Any specific use cases you were thinking of?

In my case I have a route that's only used in testing, this is perfect for that.

If you need specific routes for testing, shouldn't you just define them inside the test?
I'm talking about something like

framework/tests/Routing/RoutingRouteTest.php

Lines 54 to 58 in 5a880cc

	$router = $this->getRouter();
	$router->get('foo/bar', function () {
	return 'hello';
	});
	$this->assertSame('hello', $router->dispatch(Request::create('foo/bar', 'GET'))->getContent());

instead of hardcoding them inside your project code?

[shaedrich]

This test doesn't actually test if when() works but if matches() works—this is counterintuitive to have in this PR