owner_class_has_initial_state?'s warning should not be shown if the initial_value and the machine's default are the same

[fruwe]

    # Sets the initial state of the machine.  This can be either the static name
    # of a state or a lambda block which determines the initial state at
    # creation time.
    def initial_state=(new_initial_state)
      @initial_state = new_initial_state
      add_states([@initial_state]) unless dynamic_initial_state?

      # Update all states to reflect the new initial state
      states.each {|state| state.initial = (state.name == @initial_state)}

      # Output a warning if there are conflicting initial states for the machine's
      # attribute
      if owner_class_has_initial_state?
        warn(
          "Both #{owner_class.name} and its #{name.inspect} machine have defined "\
          "a default for \"#{attribute}\". Use only one or the other for defining "\
          "defaults to avoid unexpected behaviors."
        )
      end
    end

this shows the warning even if the initial value set in the model is the same as in the machine (in my case ActiveRecord).

The database design is quite strict, so I can not remove the default, but would anyway like to have the default in the code, to make the code more readable. How about checking the values against the defaults? If the default is the same, then do not show the message.

Thanks

[obrie]

That's a fair point. It should only give a warning if the values are different. I'll take a look at this in the next release. Thanks :)

[fruwe]

Thanks! Great!

[obrie]

Thanks again for reporting this!