-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Age of frozen beans is misleading #863
Comments
Hey @reox,
The age is already rightly calculcated, but you'd need to wait for 90 days, that the aging-counter will "rise".
The idea behind this was to not see like "852 days old bean" rather like: You've finished the bean within 30days off roast - if you got a better title, I'm more then happy to tackle this in the next verison.
Maybe two have two fields to display would be the easiest, but still there would be a good naming for it Have a great cup of coffee and a good slide into 2025 :) |
That means right now, the "stale-factor" is 90?
That is true!
Well yeah, I can understand that. I also do not have a good name... I would assume "days since roast" and "days since frozen" would be good - but I don't know about other users' use-cases.
Thanks, you too! And keep up the great work! |
Correct. Referencing to the Manchester Coffee Archive: https://manchestercoffeearchive.com/freezing-coffee/
Days since frozen would be a special setting just for "frozen" beans, I'll think a bit in it in the future. |
interesting! Well, for decaf coffee that is certainly not the case :D Maybe a quick fix would be to have this factor as a setting? In that case I could just set it to 1 to get back the old behavior :D |
Frozen beans keep their age at time of freezing. While I can understand the intention, I find it a bit misleading:
I would not mind to get back the old behavior, i.e., roasted age really shows the days since roasting, independent of frozen or thawed beans. Another option would be to let the user decide and have an option to toggle or to be able to show both times as a customization setting.
The text was updated successfully, but these errors were encountered: