-
Notifications
You must be signed in to change notification settings - Fork 8
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
Hour-level granularity does not work #177
Comments
Great catch. I don't believe that we've ever tried this at more than a day-level granularity. Are you interested in submitting a PR to make this enhancement? |
I was barely able to install the action—I'm not quite at the level of adding features quite yet! Sorry. |
https://www.npmjs.com/package/parse-reminder is the package we use to parse natural language reminders into who, what, and when. They have an example of:
So your 4 hour request is actually working. > var parseReminder=require('parse-reminder')
> parseReminder('remind me set a due date in 4 hours')
{ who: 'me', what: 'set a due date', when: 2023-10-04T15:14:54.000Z } We are using toLocaleDateString to format the date in the comments which doesn't show the time. Your reminder should work, as long as you have your reminder action running on an hourly frequency it will remind you. So this is probably a formatting "bug". But since the time at which you will be notified is based on the frequency of your reminder action, it will not always be accurate to show the time. So I'm inclined to leave it as is. Thoughts? |
In my experience, it did not wait 4 hours. It triggered almost immediately.
So I think there's probably still a real bug in there somewhere.
…On Wed, Oct 4, 2023 at 8:17 PM steveoh ***@***.***> wrote:
https://www.npmjs.com/package/parse-reminder is the package we use to
parse natural language reminders into who, what, and when. They have an
example of:
remind me in 10 minutes to change the laundry
So your 4 hour request is actually working.
> var parseReminder=require('parse-reminder')> parseReminder('remind me set a due date in 4 hours'){ who: 'me', what: 'set a due date', when: 2023-10-04T15:14:54.000Z }
We are using toLocaleDateString
<https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleDateString>
to format the date in the comments which doesn't show the time.
Your reminder should work, as long as you have your reminder action
<https://github.com/agrc/reminder-action> running on an hourly frequency
it will remind you.
So this is probably a formatting "bug". But since the time at which you
will be notified is based on the frequency of your reminder action, it will
not always be accurate to show the time. So I'm inclined to leave it as is.
Thoughts?
—
Reply to this email directly, view it on GitHub
<#177 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGCLRPIVJVWIDSU2UB7UOF3X5X4B3AVCNFSM6AAAAAA4GPHWJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBXHAZDQMJQGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
You're probably right. The next place to look would be the hidden comment format. We may strip the time there also. |
I think I'm affected by this issue as well. I was trying to use a 15 minute granularity for the reminders, and to test it, I defined a reminder like this:
When the create reminder action ran, this was the debug payload:
The |
The docs aren't clear on time window granularity, they only give examples:
I did not notice that these are actually all day-level granularity.
When I was testing my installation, I did
/remind me to set due date in 4 hours
This generated a reminder only a few minutes later:
NOTE: this could be considered either a documentation bug or a feature request—your call.
The text was updated successfully, but these errors were encountered: