London | 26-ITP-Jan | Miriam Jorna | Sprint 3 | Alarmclock#1192
London | 26-ITP-Jan | Miriam Jorna | Sprint 3 | Alarmclock#1192miriamjorna wants to merge 12 commits intoCodeYourFuture:mainfrom
Conversation
This comment has been minimized.
This comment has been minimized.
2 similar comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
cjyuan
left a comment
There was a problem hiding this comment.
Currently, when starting a new countdown, the application does not always return to a clean initial state, which can lead to inconsistent behavior between runs.
Consider introducing a dedicated reset function to return the app to a clean initial state, and call this function before starting a new countdown to help ensure consistency.
Hint: a user may not click the "Stop" button first before starting a new count down.
| if (seconds <= 0) { | ||
| alert("The number of seconds must be more than 0 please"); | ||
| return; | ||
| } |
There was a problem hiding this comment.
Indentation is off.
Have you installed the prettier VSCode extension and enabled "Format on save/paste" on VSCode,
as recommended in
https://github.com/CodeYourFuture/Module-Structuring-and-Testing-Data/blob/main/readme.md
?
If you have enabled "Format on save" but it is not working, it is likely that you haven't assign a formatter for JS file. This could happen if you have zero or multiple extensions that can format .js file.
If you have installed "Prettier" extension. To assign it as the formatter of JS code, you can try:
- Use "Format document" to format the JS file. Sometimes, VSCode will ask you to choose a formatter, and you can manually select "Prettier".
- Edit
settings.jsonand set Prettier as the default formatter for JS.
See: https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode
There was a problem hiding this comment.
Oh, my apologies, I inserted that and did not prettify it after doing so. Tbh I would normally have done that by hand quickly. Just forgot.
cjyuan
left a comment
There was a problem hiding this comment.
Indentation is a bit off. Manual indentation is a good habit but enabling auto-format can save time and help clean up trailing space. The latter is easy to miss when we format code manually.
| function pauseAlarm() { | ||
| audio.pause(); | ||
| } | ||
|
|
There was a problem hiding this comment.
Oh no! Have I been careless cleaning up the pause button issue? Not the first time I've confused the script term "pause alarm" vs. the human term "stop alarm", apologies!
| clearInterval(countdownId); | ||
| updateDisplay(0); // replaces the manual textContent line | ||
| document.body.classList.toggle("alarm-activated", false); | ||
| } |
There was a problem hiding this comment.
Shouldn't this function, resetAlarm() be called in setAlarm()?
You should also reset the audio because the user may not click the Stop button before starting a new countdown.
There was a problem hiding this comment.
Implemented. Thank you for your time!
|
Changes look good. |

Self checklist
Changelist
Made a working alarm clock.
The page changes colour when the alarm goes off.
I've made a colour reset provision for when the alarm is paused (=what the user perceives as turning it off).
Noticed input could be negative; have made sure only positive integers can now be used to set the time.