- Joined
- Dec 10, 2016
- Messages
- 12
- Reaction score
- 4
- Points
- 3
Title says it, dealing with snapshots is a PITA. They clutter up my recipes. I know I can toggle their visibility, but I have to leave them on if I want to find an old version of the recipe. Identifying the old version is very difficult with the current system.
Here's my story:
As somebody who is continually evolving my recipes, I would like to keep a historically sorted record of the changes in my recipe without cluttering my recipes UI. Ideally, I could see all "released" versions of my recipe when I open up a recipe.
Additionally, when I change a recipe, past brew sessions use the update recipe. This is not right, and certainly isn't expected behavior from the customer's perspective. The updated session should always link to the recipe that was actually used during the session. I know the answer to this is to create a snapshot, but I've already established that snapshots are annoying because they create clutter in my recipes.
I like to make my recipes public, but I think it would be cleaner to have all versions of a recipe self contained within the main recipe, instead of having dangling snapshots all over the place. If the user wants to completely disconnect a copied recipe from the original, then they can copy the recipe, using the functionality you've already provided.
We need a better way to organize recipes. I enjoy using your tools, but this is pretty close to a deal breaker for me. I can't stand losing my recipe data for past brew sessions when I update a recipe. The recipe creation/update process is a bad experience for me through brewers friend.
Thanks,
Dustin
Here's my story:
As somebody who is continually evolving my recipes, I would like to keep a historically sorted record of the changes in my recipe without cluttering my recipes UI. Ideally, I could see all "released" versions of my recipe when I open up a recipe.
Additionally, when I change a recipe, past brew sessions use the update recipe. This is not right, and certainly isn't expected behavior from the customer's perspective. The updated session should always link to the recipe that was actually used during the session. I know the answer to this is to create a snapshot, but I've already established that snapshots are annoying because they create clutter in my recipes.
I like to make my recipes public, but I think it would be cleaner to have all versions of a recipe self contained within the main recipe, instead of having dangling snapshots all over the place. If the user wants to completely disconnect a copied recipe from the original, then they can copy the recipe, using the functionality you've already provided.
We need a better way to organize recipes. I enjoy using your tools, but this is pretty close to a deal breaker for me. I can't stand losing my recipe data for past brew sessions when I update a recipe. The recipe creation/update process is a bad experience for me through brewers friend.
Thanks,
Dustin