Fixing failures against Mongoid master.

[durran]

Mongoid 2.3 (current master) has some internal changes around the way that default attributes are applied that broke the current state_machine implementation. This pull request addresses those issues.

Note there are 2 tests that I commented on in which I thought the expectation of the test (as the test was named) was incorrect. I changed these tests to pass, but the assertion does not match the expectation anymore. I do believe though the assertions are correct as I would not anticipate anything to show up in the dirty tracking when the state attribute has not actually changed itself:

https://github.com/durran/state_machine/blob/mongoid-2.3-fixes/test/unit/integrations/mongoid_test.rb#L660
https://github.com/durran/state_machine/blob/mongoid-2.3-fixes/test/unit/integrations/mongoid_test.rb#L665

I also tested against our current applications and all our tests there are passing.

Note: Mongoid 2.3.0 will be released this weekend.

My apologies for the trailing whitespace removal on the changed files - I have git hooks that just automatically do it.

[durran]

Note that the official 2.3.0 release is out. This is safe to pull in now.

[yfeldblum]

@obrie Please review, merge, and issue a patch-level release.

This is blocking for anyone using both state_machine and mongoid and wanting to upgrade to mongoid-2.3.

[yfeldblum]

@durran Any chance you can push a commit without any whitespace changes?

[huug]

As of v2.2 of mongoid seems to have several issues with state_machine
@durran will they all be solved with this pull-request?

[durran]

Yes we're using state machine just fine here with the changes in this pull. We're just pointing directly at my branch for now.

[obrie]

Hey guys -

Thanks for the pull request! I sincerely apologize for finding little time to take a look at these issues lately. I'll be able to look at all of them (including your e-mails) in the coming days and likely have a new release within the next week.

[obrie]

Thanks again to everyone, especially @durran, supporting this pull request. I left out the changes to fix the loopback failures mostly because that's a problem I need to fix across all of the ORM integrations and will be part of a major 1.1.0 release instead.

A minor release with this patch will be released this weekend.