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
puh, i don't know. But I also think we're creating a problem out of thin air.
What's that real value of having an archive? Because this Issue is not an Issue without the archive and if the archive isn't really necessary then we could spend time on more important issues. I'm sceptical of the business/user value of having the archive view.
I think I got an idea to solve this easily!! We change the Item-model and remove the picked-flag, But use the quantity as picked, so we only display items with quantity > 0 and if the user picks an item we set quantity = 0. Then, we could just find the "old" item and set the quantity to 1 when a user adds it again. This would reduce duplicates I suppose, but leaves the question whether this is of real value to the user or not.
Thats probalby a good idea. I like having this feature when adding new items so it can check if I am readding an item.
But if any item is always added again and again and again, we bloat the database for no reason. That maybe an even more interesting point
If an item has the same name then it should be reused instead of created new
The text was updated successfully, but these errors were encountered: