Ruby On Rails : Status code `:unprocessable_entity` is deprecated and will be removed in a future version of Rack.

[XAJX179]

Checks

• This is not a duplicate of an existing issue (please have a look through our open issues list to make sure)
• I have thoroughly read and understand The Odin Project Contributing Guide
• Would you like to work on this issue?

Describe your suggestion

Status code :unprocessable_entity is deprecated and will be removed in a future version of Rack.

use :unprocessable_content instead.

Path

Ruby / Rails

Lesson Url

https://www.theodinproject.com/lessons/ruby-on-rails-controllers

(Optional) Discord Name

No response

(Optional) Additional Comments

No response

[JoshDevHub]

Thanks for making this @XAJX179

It probably is good for us to switch to showing :unprocessable_content eventually, but I'm not sure if it'd be good to do right now. The Rails guides and documentation still show :unprocessable_entity all over the place, and that can get confusing.

Additionally, using unprocessable_entity in your Rails code doesn't raise any deprecation warnings. This is because Rails has merged a patch that allows developers to use either one. The deprecation you're seeing in your code is actually from devise library code (I can tell from reading the stack trace). I assume this is because it inserts itself into the Rack middleware outside of Rails's control. This is something devise will need to fix on their own. You can probably quiet the deprecation in your own code by writing:

# config/initializers/devise.rb

Devise.setup do |config|

  # remove or comment this out if it's there
  config.responder.error_status = :unprocessable_entity

  # add this
  config.responder.error_status = :unprocessable_content
end

I'll throw this in backlog for right now and talk to the team about it some.

[github-actions]

This issue is stale because it has had no activity for the last 30 days.

[Eruis2579]

hi, @JoshDevHub
Can you assign this to me?

[CouchofTomato]

This isn't a change we want to make yet. @Eruis2579

Rails and associated libraries will probably take care of this themselves