You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In short, this example stops at the same point as the tutorial challenge, which was creating forms for create, modify, delete, of books. It does not show any code for bookinstances.
However if you were to implement a bookinstance code, assign a book, and then you delete the book you get an error - because the book model requires you cannot delete a book unless all its instances are first deleted.
What did you expect to see?
We need to implement the bookinstance stuff as well (to ease testing) and override the book implementation to handle the error and provide a new view in this error case.
We should also create a Test for this case in the test cases, though that is not essential.
Output logs
Nope.
Do you have anything more you want to share?
Nope
The text was updated successfully, but these errors were encountered:
caugner
added
bug
Indicates an unexpected problem or unintended behavior.
and removed
needs triage
Triage needed by staff and/or partners. Automatically applied when an issue is opened.
labels
Oct 2, 2023
Before submitting the issue, confirm that you've checked everything in the following list, and mark them as completed here:
What was incorrect, unhelpful, or unexpected?
The problem is described here mdn/content#27895 and the "base" of the solution is described in comment here: mdn/content#27895 (comment)
In short, this example stops at the same point as the tutorial challenge, which was creating forms for create, modify, delete, of books. It does not show any code for bookinstances.
However if you were to implement a bookinstance code, assign a book, and then you delete the book you get an error - because the book model requires you cannot delete a book unless all its instances are first deleted.
What did you expect to see?
We need to implement the bookinstance stuff as well (to ease testing) and override the book implementation to handle the error and provide a new view in this error case.
We should also create a Test for this case in the test cases, though that is not essential.
Output logs
Nope.
Do you have anything more you want to share?
Nope
The text was updated successfully, but these errors were encountered: