You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
Would it be nice to have a new assertRedirectToRoute method for easier checking of redirects? In opposite to assertRedirectTo, the new method would be more robust due to changes in the routes of the application to test.
F.e. if I change the URI in one of the routes (my-route) of my application from /foo/bar/baz to /foo-foo/bar-bar/baz-baz, I would have to modify my test case too:
Would it be nice to have a new
assertRedirectToRoute
method for easier checking of redirects? In opposite toassertRedirectTo
, the new method would be more robust due to changes in the routes of the application to test.F.e. if I change the URI in one of the routes (
my-route
) of my application from/foo/bar/baz
to/foo-foo/bar-bar/baz-baz
, I would have to modify my test case too:to
With the new method:
What do you think? I could make a pull-request for that if you would accept my proposal.
The text was updated successfully, but these errors were encountered: