Closed SergkeiM closed 2 years ago
Hm, I've dug into this a bit and can recreate the bug but it looks like it might be a bit tricky to sort out. We have to do some tricky stuff to have access to the route parameters at the right time, and it looks like some of that approach may need to be rethought to make nested groups work in this case.
Actually, can you try the current dev-main
release? I think I found a solution…
This should be fixed in 1.6.0
Hi @inxilpro apologies I didn't had time to check this, will do today and revert thank you.
Describe the bug By wrapping resource into a Route Group with {parameter}, throws an error that parameter doesn't exists,
I've tried to pass the parameter as 3rd callback, but the same result.
What version does this affect?
To Reproduce
Expected behavior Generate breadcrumbs
Additional context Throws an error:
Missing required parameter for [Route: actors.create] [URI: movies/{movie}/actors/create] [Missing parameter: movie].