Route conflict when scaffolding `session`
Hello,
when I scaffold a resource called `session` in a Jumpstart app, I get a conflict between devise routes and my resource routes when user signin. If I remove the `session` route added by the generator, everything works fine.
Any suggestions on how to best address this?
As far as I know `session` is not reserved and I should be able to name a resource session.
Thanks
when I scaffold a resource called `session` in a Jumpstart app, I get a conflict between devise routes and my resource routes when user signin. If I remove the `session` route added by the generator, everything works fine.
Any suggestions on how to best address this?
As far as I know `session` is not reserved and I should be able to name a resource session.
Thanks
Thanks for your response.
To be clear, I'm not getting this error when trying a route on my `session` resource.
I'm getting this error when signing in. Signin is handled by `devise` and its `sessions` controller and I think this is where the route conflict lies.
If I rename my resource `msession` , sign in works fine, but fails it you scaffold a resource named `session`.
Steps to reproduce:
1. from a clean jumpstart code base, run `rails g scaffold session name:string user:references`
2. run migration
3. try signing in
Thanks
To be clear, I'm not getting this error when trying a route on my `session` resource.
I'm getting this error when signing in. Signin is handled by `devise` and its `sessions` controller and I think this is where the route conflict lies.
If I rename my resource `msession` , sign in works fine, but fails it you scaffold a resource named `session`.
Steps to reproduce:
1. from a clean jumpstart code base, run `rails g scaffold session name:string user:references`
2. run migration
3. try signing in
Thanks
Notifications
You’re not receiving notifications from this thread.