set deleted to false instead of unsetting when calling restore() #150
+3
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I put up another PR that does this before seeing yours. Apologies. Here's mine: #157 |
|
@dsanel would you be open to transferring this project to the mongoosejs GitHub org and handing maintenance over to the Mongoose team? No pressure, this is your project if you want to keep maintaining it, I wanted to ask just in case. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix Automattic/mongoose#14338
It looks like this commit: b8c3cea made it so that the
restore()static would unsetdeletedversus setting it tofalse, which is backwards breaking for projects that useuse$neOperator: false.