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
Currently cookbooks will throw an error if there's another cookbook with the same name. Similar to recipes, we should allow this as long as the slug is different.
We want this since two different households might have the same common cookbook name (e.g. Drinks). Since cookbooks are tied to households, they may not know a cookbook name is taken already.
Proposed/Possible Solution(s)?
Make sure the API handles duplicate names correctly (e.g. incrementing the slug, like it does for recipes)
Make sure the frontend handles this fine
The text was updated successfully, but these errors were encountered:
What is the problem this task addresses?
Currently cookbooks will throw an error if there's another cookbook with the same name. Similar to recipes, we should allow this as long as the slug is different.
We want this since two different households might have the same common cookbook name (e.g. Drinks). Since cookbooks are tied to households, they may not know a cookbook name is taken already.
Proposed/Possible Solution(s)?
The text was updated successfully, but these errors were encountered: