-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
findByIdAndRemove depricated? #30152
Labels
Content:Learn:Express
Learning area Express docs
Comments
Shahad7
added
the
needs triage
Triage needed by staff and/or partners. Automatically applied when an issue is opened.
label
Nov 9, 2023
hamishwillee
removed
the
needs triage
Triage needed by staff and/or partners. Automatically applied when an issue is opened.
label
Nov 13, 2023
Thanks very much - this should be fixed by #30230 |
Hey, so should i close the issue now? This is the first time i am opening
an issue
…On Mon, 13 Nov 2023, 9:08 am Hamish Willee, ***@***.***> wrote:
Thanks very much - this should be fixed by #30230
<#30230>
—
Reply to this email directly, view it on GitHub
<#30152 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJRLDESR27CNVTOWIFV447DYEGI3FAVCNFSM6AAAAAA7EHJZCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGQZDQMJSG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi @Shahad7 No need thanks. If you look at the issue I created it has We do it that way because sometimes a reviewer will reject a PR fix as "not good enough" - in which case this issue would remain open until it was actually fixed. |
Oh okayy
…On Mon, 13 Nov 2023, 10:42 am Hamish Willee, ***@***.***> wrote:
Hi @Shahad7 <https://github.com/Shahad7> No need thanks. If you look at
the issue I created it has Fixes 30152 in the description. What that
means is that as soon as the PR is merged this issue will automatically
close.
We do it that way because sometimes a reviewer will reject a PR fix as
"not good enough" - in which case this issue would remain open until it was
actually fixed.
—
Reply to this email directly, view it on GitHub
<#30152 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJRLDEX6V3IE74OD574VF2DYEGT3FAVCNFSM6AAAAAA7EHJZCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGQ4DQMZXGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
MDN URL
https://developer.mozilla.org/en-US/docs/Learn/Server-side/Express_Nodejs/forms/Delete_author_form
What specific section or headline is this issue about?
delete author post route
What information was incorrect, unhelpful, or incomplete?
I believe the findByIdAndRemove function doesn't exist anymore. It was throwing an error and I couldn't find the function in the mongoosejs ofiicial docs. I was following the tutorial
What did you expect to see?
a function that deletes the record ofc!
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
No response
MDN metadata
Page report details
en-us/learn/server-side/express_nodejs/forms/delete_author_form
The text was updated successfully, but these errors were encountered: