attribute_changed? and related should cope with aliases

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • 4.0.0 final
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Couldn't for the life of me figure out why my uniqueness validators weren't running. Turns out they are calling out to attribute_changed? before doing anything and the latter didn't understand aliases.

      The attached should fix of Changeable's public-facing methods. The other methods should never be passed aliases in the first place, if I understand correctly, and thus don't require patching.

              Assignee:
              Unassigned
              Reporter:
              Niels Ganser
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: