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
I have the date format setting for the DYE extension set to MDY. My most recent bag is entered as 09.02.2024 (i.e. September 2, 2024), and the extension is interpreting it correctly since it says is 19 days off roast. The visualizer, on the shot and roasters pages, now displays the roast date, but it's showing as February 09, 2024. So, if the date parses it's incorrect, but many dates will fail to parse properly.
To Reproduce
Steps to reproduce the behavior:
Enter bag roast date with the DYE extensions set to MDY (and maybe anything other than DMY, I did not check) and upload a shot
Check the date displayed for the shot
Expected behavior
The date format should be taken into account when parsing dates.
Desktop (please complete the following information):
OS: Windows 11
Browser: Chrome 129.0.6668.59
The text was updated successfully, but these errors were encountered:
…the setting to format it as the user wants is a DYE setting, not a global setting you can find in the file
I think the app would handle dates with numbers larger than 12 on the second position automatically, but it can't determine what "09.02.2024" stands for since it's ambiguous. It assumes it's not MDY since, as far as I know, that's only used in 1 out of 195 countries in the world 😂
I will need to add a setting for this I believe. Similar to Fahrenheit. Huh, maybe I could even use that, since that's also not used much outside of USA. 😅
I think the app would handle dates with numbers larger than 12 on the second position automatically, but it can't determine what "09.02.2024" stands for since it's ambiguous. It assumes it's not MDY since, as far as I know, that's only used in 1 out of 195 countries in the world 😂
True, but it is the first option 😉. Obviously an easy fix is just to change formats, which is what I'm going to do for now.
FYI - Changing the bag date first in the visualizer updated everything, that's really nice, and then the next shot (now DMY) synced with the previous bag by date.
I will need to add a setting for this I believe. Similar to Fahrenheit. Huh, maybe I could even use that, since that's also not used much outside of USA. 😅
Is it weird that I use US date format and Celsius 🤣.
Describe the bug
I have the date format setting for the DYE extension set to
MDY
. My most recent bag is entered as09.02.2024
(i.e. September 2, 2024), and the extension is interpreting it correctly since it says is 19 days off roast. The visualizer, on the shot and roasters pages, now displays the roast date, but it's showing asFebruary 09, 2024
. So, if the date parses it's incorrect, but many dates will fail to parse properly.To Reproduce
Steps to reproduce the behavior:
MDY
(and maybe anything other thanDMY
, I did not check) and upload a shotExpected behavior
The date format should be taken into account when parsing dates.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: