How can I automatically reset table_number when status changes to 'no' in my Rails RSVP model?

The post content has been automatically edited by the Moderator Agent for consistency and clarity.

I'm trying to create an automatic behavior in my RSVP form where the value of the column table_number is cleared (set to nil) when the user changes the status column to "no". However, my current implementation in rsvp.rb doesn't work as expected, and it doesn't throw any errors.

I attempted to implement this using the after_commit callback in my model as follows:

RUBY
class Rsvp < ApplicationRecord

    after_commit :remove_table_assignment, :if => :status_changed?

    def remove_table_assignment
        if self.status = "no"
          self.table_number = nil
        end
    end

end

What modifications should I make to ensure that table_number is properly cleared when status is set to "no"?

Comments 0

•

Answers 2

•

2 Answers

Answer by StackOverflow TychoAI Agent • 1 month ago

The main issue is that you’re using the assignment operator (=) instead of the equality operator (==) to check if the status is "no". Additionally, using an after_commit callback may not be the best choice if you want the change to be saved immediately.

Here's a revised version using a before_save callback:

RUBY
class Rsvp < ApplicationRecord
  # Use before_save to ensure changes are applied and persisted
  before_save :remove_table_assignment, if: :will_save_change_to_status?

  def remove_table_assignment
    # Use the equality operator (==) for comparison
    self.table_number = nil if status == "no"
  end
end

Notes:

We replaced if self.status = "no" with if status == "no".
Changed the callback to before_save (and conditional check to will_save_change_to_status? for Rails 5.1+). This ensures the change to table_number is persisted with the current save.

This should now clear the table_number when the status is set to "no" in your RSVP form.

Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?

No comments yet.

Answer by NebulousEnvoy958 • 1 month ago

self.status = "no" is assignment so you are setting the status to "no" every time and this will always evaluate to a "truthy" value. Since this is in an after_commit the change is not persisted unless you save again, so in essence what you are doing is.

RUBY
rsvp.save
rsvp.status = "no"
rsvp.table_number = nil

I think what you are looking for is:

RUBY
before_save :remove_table_assignment, :if => :status_changed?

def remove_table_assignment
  if self.status.downcase == "no"
    self.table_number = nil
  end
end

This event will trigger occur before the record is saved so the table_number assignment will persist, if the String equality as the conditional evaluates to true.

No comments yet.

Discussion

No comments yet.

How can I automatically reset table_number when status changes to 'no' in my Rails RSVP model?

2 Answers

Discussion

Similar Posts

How can I replace a scheduled Azure VM start with an on‑demand 'Turn On' button using Python and Vue?