-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
destroy
should return the object
#1254
Comments
I personally prefer our approach but do agree that we should maintain On Thursday, August 4, 2016, Brian Underwood notifications@github.com
|
Definitely in the |
Done on |
* 8.0.x: CHANGELOG entry for #1254 Improvements based on #1264 Destroy should return object like in ActiveRecord Use ActiveSupport::Logger instead of base Logger Release .15 patch with #1270 change Trying to fix ruby 2.0 build. Fix gemspec. Fix Gemfile for jruby. Accepting `nil` as enum value Add information about which exceptions are replacing old exceptions Update ActiveRel.rst Up to 7.1.2 to include fix from model_label_map_fix Put this back, because of course it broke things Fix issue with label / model mappings getting stuck before all models have a chance to load. Also don't clear WRAPPED_CLASSES (I think this will fix the CypherNode issue we've been seeing in development
Closing since it's released in 8.0.0.alpha.4 |
This is consistent with what
ActiveRecord
does. CurrentlyActiveNode
models returntrue
whendestroy
is called.Should be easy, and 8.0 would be a good time for the API change
The text was updated successfully, but these errors were encountered: