added another edgecase to time formatting

Author: marthak1

Sprint-1/3-mandatory-interpret/2-time-format.js

@@ -1,12 +1,12 @@
-const movieLength = 8784; // length of movie in seconds
+const movieLength = 9; // length of movie in seconds
 
 const remainingSeconds = movieLength % 60;
 const totalMinutes = (movieLength - remainingSeconds) / 60;
 
 const remainingMinutes = totalMinutes % 60;
 const totalHours = (totalMinutes - remainingMinutes) / 60;
 
-const result = `${totalHours}:${remainingMinutes}:${remainingSeconds}`;
+const result = `${totalHours}:${String(remainingMinutes).padStart(2, "0")}:${String(remainingSeconds).padStart(2, "0")}`;
 console.log(result);
 
 // For the piece of code above, read the code and then answer the following questions
@@ -33,4 +33,5 @@ console.log(result);
 // f) Try experimenting with different values of movieLength. Will this code work for all values of movieLength? Explain your answer
 // No. Not for all possible values of movieLength, some EdgeCases are: 
 //1. when movieLength is of negative value, the maths produces negative time and its illogical for a movie duration
-//2. if movieLength is not a number, its produces "NAN" and this breaks mathematically
+//2. if movieLength is not a number, its produces "NAN" and this breaks mathematically
+//3. what if movieLength is less than 10? if movieLength is let say 9 , without proper formatting it will look like this 0:0:9 but with 0 padding it looks better like this 0:00:09

Sprint-1/3-mandatory-interpret/3-to-pounds.js

@@ -24,4 +24,7 @@ console.log(`£${pounds}.${pence}`);
 // Try and describe the purpose / rationale behind each step
 
 // To begin, we can start with
-// 1. const penceString = "399p": initialises a string variable with the value "399p"
+/* 1. const penceString = "399p": initializes a string variable with the value "399p"
+   2. const penceStringWithoutTrailingP = This stores the substring of penceString without a trailing p, so "399p" becomes "399"
+   3. const paddedPenceNumberString= 
+*/