-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Discord Timestamps] Displayed result time has incorrect time range (am/pm) #16592
Comments
Thank you for opening this issue! 🔔 @thewilloftheshadow @feyli @hrueger you might want to have a look. 💡 Author and Contributors commandsThe author and contributors of
|
Thanks for reporting this! I'll have a look at it ;) |
It should only take one character in the code to fix this haha, I'll try to do it now |
…ion (raycast#16592) - Modify the condition in the amPm function to include 12 as PM. - This change ensures that the function correctly identifies noon as PM.
Pull request is up and waiting for approval! |
* fix(timestamps.ts): update amPm function to include noon in PM condition (#16592) - Modify the condition in the amPm function to include 12 as PM. - This change ensures that the function correctly identifies noon as PM. * Update CHANGELOG.md * Update CHANGELOG.md and optimise images --------- Co-authored-by: raycastbot <bot@raycast.com>
Merged! |
@feyli it seems like it's working as expected now! Thank you so much for the quick fix |
Extension
https://www.raycast.com/theshadowdev/discord-timestamps
Raycast Version
1.89.1
macOS Version
Sequoia 15.2 (24C101)
Description
When generating a new timestamp set to 12 pm (or any time between 12:00 pm and 12:59 pm), it is shown as AM. It works fine with 12 am and 1 pm (13).
It might be because I have my system time set to 24 hours?
Steps To Reproduce
Note: This seems to be a UI only issue, as the timestamp is correctly set to the right time (am or pm). Anyways, is misleading and makes users think that the timestamp will be incorrect
Current Behaviour
Any time between 12:00 pm and 12:59 pm is shown as AM
Expected Behaviour
Any time between 12:00 pm and 12:59 pm should be shown as PM
The text was updated successfully, but these errors were encountered: