Add alarm extension

[aurnik]

Description

This extension parses text passed as an argument to create alarms. Alarms can be set using a specific date and time or using a duration.

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! 🚀

We will aim to make the initial review within five working days. Once the PR is approved and merged, the extension will be available on our Store.

[pernielsentikaer]

Hi @aurnik 👋

Thanks for your contribution 🔥 It looks like we have something very similar in the store already, could you check that out?

[aurnik]

Hey @pernielsentikaer thanks for getting back to me -- yes I did see that extension but thought this provided some useful differences:

1. The mentioned extension uses a background service running on a 1 minute interval to set its notifications, whereas this one schedules the notification using a shell command. This avoids the regularly running background service and notifies the user at the exact time they've scheduled.
2. This extension allows creating alarms that don't have a "topic", such as setting an alarm for 15 minutes (and these are created without going to a separate view using command arguments)
3. This has the additional setting to use dialog boxes instead of notifications (can be seen even when Focus is on)

It seemed like adding these to that extension would fundamentally change the design choices that the developer made, so I rolled this out separately. I'm open to any feedback though, appreciate your time.

[pernielsentikaer]

Hi 👋

Thanks for your contribution 💪

I have now tested your extension, and I have some feedback ready for you:

• The command List Alarms suffers from Empty state flicker

• I would add a confirmAlert before deleting

• Would be nice with an icon here 🙂

• Why is refresh.ts necessary, I can't figure out what it brings, can you clarify that for me 🙂

I'm looking forward to testing this extension again 🔥

Request a new review when you are ready. Feel free to contact me here or at Slack if you have any questions.

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[raycastbot]

This issue has been automatically closed due to inactivity.

Feel free to comment in the thread when you're ready to continue working on it 🙂

You can also catch us in Slack if you want to discuss this.

[aurnik]

• The command List Alarms suffers from Empty state flicker

✅ Fixed

• I would add a confirmAlert before deleting

✅ Fixed

• Would be nice with an icon here 🙂

Which part are you referring to? At least in that photo, I'm seeing icons for the extension itself as well as each list item.

• Why is refresh.ts necessary, I can't figure out what it brings, can you clarify that for me 🙂

Because this extension schedules the timers instead of constantly checking if the time is up, this file handles the actual scheduling. It only needs to be run once, but it does need to happen in the background or else the user would need to run a command every time Raycast was started in order to reschedule alarms . The interval could be anything though. If there's a better way to do this, I'm happy to change it.

Also, I posted in Slack but I'm unable to update this with npm run publish. Do I need to close this and create a new PR?

[mil3na]

Hey @aurnik ! Is this PR ready for re-review? Are you still having issues with the publish command?

[aurnik]

@mil3na Thanks for getting back, and yes I'm still unable to use the publish command.

This was my message from the Slack group:

Hey team, I'm trying to publish updates to an extension I submitted some time ago, and I've updated my fork of raycast-extensions but now when I try to run npm run publish it tells me I need to pull new contributions, and when I try doing that I get an error fatal: Not possible to fast-forward, aborting. from the command git pull origin ext/alarm --ff-only. Any advice on how to move forward?

The git pull command is a part of npx @raycast/api@latest pull-contributions, and this is my repo for the extension on its own.

[pernielsentikaer]

I just asked my colleagues to have a look on the thread so we can continue here 🙂

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[pernielsentikaer]

Pinged in Slack, are you still having the issue @aurnik

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[raycastbot]

This issue has been automatically closed due to inactivity.

Feel free to comment in the thread when you're ready to continue working on it 🙂

You can also catch us in Slack if you want to discuss this.