-
Notifications
You must be signed in to change notification settings - Fork 18
Before/After X days ago #56
Comments
Haha, no worries; someone else asked about this previously as well. Check out this explanation and let me know if it clears it up: #35 (comment). If so, I'll clean it up, move it to the faq and link it from the editor. Or, maybe there's a better way to name it that removes the ambiguity? I'd love to hear your thoughts how you'd naturally think about this. |
Can you change the wording to "Within" rather than before, and "More than" for after? Or are there other arguments that rely on "before" Or did I get these backwards again ha ha |
Actually if last played is less than 15 days ago, then that means it was played a long time ago... So when I change the way I think about it all is good but I think within and more than makes more sense to me. |
Hi Simon Thanks for the quick reply and for the link - it helped. Could you add a date picker to differentiate relative and absolute date:
This will give users 2 time format options:
The form field UI will still be the same with maybe a visual cue in the form of a calendar icon like below: Thanks and well done. |
It's not clear since there's no example, but absolute datetimes will be parsed currently. I'd like to avoid changing the interface much since it's generated by third party code that's a pain to work with 😁 I think phrasing this more like a time range might be the way to go. What about rewording to "between now and" and "earlier than"? This reads pretty well to me for all the cases:
We'd also want to add an absolute datetime example to the page. |
That should make it clearer, thanks |
Thanks for the feedback! |
Thank you so much for this extension.
I am a little bit confused by the use of before/after in dates like below: (sorry if this is obvious)
Last Played
:Before
:15 Days Ago
(described aslastPlayed < 15 days ago
)Last Played
:After
:15 Days Ago
(described aslastPlayed > 15 days ago
)I will be grateful if you provide a brief explanation.
The text was updated successfully, but these errors were encountered: