London | 26-ITP-January | Eugenie Ahangama | Sprint 2 | coursework/sprint 2

[Eugenie-A]

Learners, PR Template

Self checklist

• I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
• My changes meet the requirements of the task
• I have tested my changes
• My changes follow the style guide

Changelist

I worked through the Sprint 2 exercises by going through the starter code, identifying the main errors and making sure I understood why the logic wasn't working. I then wrote tests in the debug section to clearly show the issues before fixing anything. After that, I implemented the correct JavaScript behaviour so the function produced the right results. Finally, in the interpret task, I explained what the original code was doing, why it failed and how my fixes solved those problems.

MDN References I used:
String.prototype.slice()
Number() constructor
Template literals
console.assert()
String.prototype.split()
Array.prototype.map()
Remainder operator (%)
String.prototype.padStart()
String.prototype.substring()
String.prototype.replace()
String.prototype.trim()
String.prototype.toUpperCase()
Function parameters
Return

Questions

What's the best way to structure a debugging process?

[cjyuan]

What type of value do you expect your function to return? A number or a string?
Does your function return the type of value you expect?

Different types of values may appear identical in the console output, but they are represented and treated differently in the program. For example,

  console.log(123);              // Output 123
  console.log("123");            // Output 123
  
  // Treated differently in the program
  let sum1 = 123 + 100;         // Evaluate to 223 -- a number
  let sum 2 = "123" + 100;      // Evaluate to "123100" -- a string.