Minitimer - #15
Merged
Merged
Conversation
Ne değiştirdim? SPEC.txt dosyasındaki stop komutu yönergelerini güncelleyerek yeni bir hata yönetimi kuralı ekledim. Neden değiştirdim? Önceki belgede, kullanıcının zaten 'STOPPED' durumdaki bir sayacı tekrar durdurmaya çalışması halindeki davranış tanımlanmamıştı. Olası mantıksal hataların önüne geçmek için bu durumu ele aldım ve programın artık açıkça "Timer #x is already stopped" mesajı yazdırmasını sağladım.
Ne değiştirdim? SPEC.txt dosyasındaki stop komutu yönergelerini güncelleyerek yeni bir hata yönetimi kuralı ekledim. Neden değiştirdim? Önceki belgede, kullanıcının zaten 'STOPPED' durumdaki bir sayacı tekrar durdurmaya çalışması halindeki davranış tanımlanmamıştı. Olası mantıksal hataların önüne geçmek için bu uç durumu ele aldım ve programın artık açıkça "Timer #x is already stopped" mesajı yazdırmasını sağladım.
Collaborator
Please set up your file structure like above. |
…er/SPEC v2.txt What did I change? I updated the stop command specifications in the SPEC-v2.txt file to include a new error-handling rule. Why did I change it? The previous specification did not define the behavior for when a user attempts to stop a timer that is already in the 'STOPPED' state. I addressed this edge case so the program now explicitly prints a "Timer #x is already stopped" message, preventing potential logical bugs. Did I test it? Yes, I manually tested this edge case by running the stop command twice on the same timer ID. The program successfully output the new error message without modifying the file incorrectly.
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What did i change?
I updated the stop command specifications in the SPEC.txt file to include a new error-handling rule.
Why did I change it?
The previous specification did not define the behavior for when a user attempts to stop a timer that is already in the 'STOPPED' state. I addressed this edge case so the program now explicitly prints a "Timer #x is already stopped" message, preventing potential logical bugs.
Did I test it?
Yes, I manually tested this edge case by running the stop command twice on the same timer ID. The program successfully output the new error message without modifying the file incorrectly.