We've moved discussions to Discord

Route conflict when scaffolding `session`

YACIN BAHI
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
Screen Shot 2020-02-17 at 10.20.53 PM.png 307 KB
Chris Oliver
Looks to me like you're making a POST to /sessions/:id which is not a route that exists. You only have a POST route for /sessions. That's not a conflict with Devise or anything.
YACIN BAHI
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   
Chris Oliver
You've probably done something that conflicts with Devise's SessionController. You probably want to read up on Devise's routes and controllers. It uses "Session" for logging in.
Notifications
You’re not receiving notifications from this thread.