Hi. I have the same problem as you, and I want to know if you found any practical solution? I'm thinking about unsetting subdomain parameter from resolved route instance. I don't know if it will gonna work and won't cause any other problems.
UPDATE: I did something you suggested, that uses middleware. I already had special middleware class for subdomains so I just added 2 lines before calling $next($request).
$route = $request->route();
$route->forgetParameter(SUBDOMAIN_WILDCARD);
JanJ said:
Hi. I have the same problem as you, and I want to know if you found any practical solution? I'm thinking about unsetting subdomain parameter from resolved route instance. I don't know if it will gonna work and won't cause any other problems.
UPDATE: I did something you suggested, that uses middleware. I already had special middleware class for subdomains so I just added 2 lines before calling $next($request).
$route = $request->route(); $route->forgetParameter(SUBDOMAIN_WILDCARD);
VERRRRRYYYY GOOOD
very good and I think we will not give no problem
I'm a week thinking about it, and was coming to this point to remove a parameter.
Now the question is: is the most correct?
Before #parameters: array:2 [▼ "account" => "demo" "profissional" => "7" ] After #parameters: array:1 [▼ "profissional" => "7" ]
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community