Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use known-name routes because redirection targets can conflict with actual names #36

Open
airblade opened this issue Apr 17, 2024 · 0 comments

Comments

@airblade
Copy link
Owner

airblade commented Apr 17, 2024

Currently the way to configure where QuoVadis redirects the user after, e.g., logging in is to specify a route with the name :after_login:

get '/dashboard', to: 'dashboards#show', as: :after_login

But that means if you want to give the route its "own" name, :dashboard, you need to duplicate the routes:

get '/dashboard', to: 'dashboards#show', as: :dashboard
get '/dashboard', to: 'dashboards#show', as: :after_login

This is a little inelegant.

@airblade airblade changed the title Use known-name routes as redirection targets can conflict with actual names Use known-name routes because redirection targets can conflict with actual names Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant