In the rule editor, when a Date condition (e.g. 'Date added is older than') has its unit set to something other than Days (e.g. Months, Weeks), editing the number input causes the unit dropdown to silently reset to 'Days'. This happens even though the unit was explicitly set to a different value beforehand.
Steps to reproduce
- Open a rule with a Date condition (e.g. 'Date added → is older than → 1 → Months').
- Click into the number field and change the value (e.g. from 1 to 2).
- Observe the unit dropdown next to it.
Expected behavior
The unit dropdown should retain whatever value it was set to (Months, Weeks, etc.) — only the number should change.
Actual behavior
The unit dropdown resets to 'Days' as soon as the number input changes, silently altering the condition's meaning (e.g. '1 Months' becomes '2 Days' instead of '2 Months') without any confirmation or warning.
Why this matters
This is easy to miss since the number and unit look independent — someone could save a rule believing it says 'older than 2 months' when it actually now says 'older than 2 days', which could cause files to be moved/trashed far earlier than intended. Worth flagging as high-severity given the Trash/Delete actions this feeds into.
Environment
- macOS version:
- Forel version:
- Install method: Homebrew / direct .dmg download
In the rule editor, when a Date condition (e.g. 'Date added is older than') has its unit set to something other than Days (e.g. Months, Weeks), editing the number input causes the unit dropdown to silently reset to 'Days'. This happens even though the unit was explicitly set to a different value beforehand.
Steps to reproduce
Expected behavior
The unit dropdown should retain whatever value it was set to (Months, Weeks, etc.) — only the number should change.
Actual behavior
The unit dropdown resets to 'Days' as soon as the number input changes, silently altering the condition's meaning (e.g. '1 Months' becomes '2 Days' instead of '2 Months') without any confirmation or warning.
Why this matters
This is easy to miss since the number and unit look independent — someone could save a rule believing it says 'older than 2 months' when it actually now says 'older than 2 days', which could cause files to be moved/trashed far earlier than intended. Worth flagging as high-severity given the Trash/Delete actions this feeds into.
Environment