Skip to content

Conversation

@kkirsche
Copy link
Contributor

Follow rails convention by returning false unless the item is valid.

@karmi
Copy link
Contributor

karmi commented Apr 11, 2015

This makes sense! Apologies for the ridiculous delay, you should have pinged me!

If you still have time & energy for the patch, can you please update it:

  1. There's been a :validate option introduced in 1fd6c0b, can we play with it?
  2. Can you please add a unit test for this?

Follow rails convention by returning false unless the item is valid.
@kkirsche
Copy link
Contributor Author

Updated with :validate option and unit tests. Please let me know if you have any questions, comments or concerns.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you run the test? subject.expects(:persisted?).returns(true) ... :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test suite of this project has never worked for me sadly so I haven't been able to outside of Travis CI

@karmi karmi closed this in 50fee81 Apr 23, 2015
karmi added a commit that referenced this pull request Apr 23, 2015
@karmi
Copy link
Contributor

karmi commented Apr 23, 2015

Fixed the tests in b660d6a and merged.

@dgmora
Copy link

dgmora commented Jan 17, 2017

Unless I'm miss understanding something, this is not fixing the important cases.

If you have stored a valid model, and then update with an invalid attribute, valid? will be true, as the model has yet not been changed, and there won't be validation

@dgmora dgmora mentioned this pull request Jan 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants