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
Describe the bug
When configuring the within-time node, I set a date range at "validForDates (year will be ignored)", save and deploy. However when I double click back into the node, my ending date in the date ranged has incremented back one day.
Example: I set my ending date to Jan 31st 2024, deploy. When I enter back into the node to check configuration (or for whatever reason) the ending date now shows Jan 30th 2024. Close and open it again and it increments back one more day again. However, when I re-set the ending date to the date I wanted, I am not asked to redeploy the flow... meaning to me at least that the initial date setting is correct and the only bug is the date being displayed, rather than the date actually being changed.
Screenshots
If applicable, add screenshots to help explain your problem.
Expected behavior
I would expect to see the exact configuration I entered when opening the node.
System information (please complete the following information):
Node Version: 20.10.0
Node-Red Version: 3.1.3
OS: Linux Mint 21, Kernel: 5.15.0-91
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
When configuring the within-time node, I set a date range at "validForDates (year will be ignored)", save and deploy. However when I double click back into the node, my ending date in the date ranged has incremented back one day.
Example: I set my ending date to Jan 31st 2024, deploy. When I enter back into the node to check configuration (or for whatever reason) the ending date now shows Jan 30th 2024. Close and open it again and it increments back one more day again. However, when I re-set the ending date to the date I wanted, I am not asked to redeploy the flow... meaning to me at least that the initial date setting is correct and the only bug is the date being displayed, rather than the date actually being changed.
Screenshots
If applicable, add screenshots to help explain your problem.
Expected behavior
I would expect to see the exact configuration I entered when opening the node.
System information (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: