Flesh-Out Exercise Tracker User Stories and Typo

In order to avoid common confusion with this project, I suggest we add something along the lines of:

interface Exercise {
  description: string,
  duration: number,
  date: Date, // Specifically: toDateString (date portion of Date object
}

interface NewUser {
  _id: string,
  username: string,
}

interface Log {
  count: number,
  log: Exercise[],
}

I expect this to be added to the description of the challenge. Something to that extent.

---

Also, there is a small typo, which can be easily fixed: from this forum post You can POST to /api/exercise/new-user with form data username to create a new user. The returned response will be an object with username and _id properties.

You can make a GET request to 👉 api/exercise/users to get an array of all users. Each element in the array is an object containing a user’s username and _id .

You can make a GET request to /api/exercise/log with […]

[ShaunSHamilton]

@raisedadead I like Nicholas’ suggestion, but would definitely want to add something like:

**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.

In all fairness, the tests could be changed to accept any JS-approved date (we have done this with the Anonymous Message Board, IIRC). The above would definitely be the easiest, though.

[risaddex]

I would like to point on this, the user’s stories say “similar with this” but in practice it actually needs to be DEEPLY equal (i needed to look into assertions from the project to check what I was missing - in this case, the date Format since my date constructor was getting my local date, which with the tests, makes the date 1990-01-01 become 1989-12-31 )

just specify that the date format is mandatory, please

sorry for my bad English, but I’ve ended up seeing more people passing for the same situation - specially with the possibly lack of information about assertions for people new to node 😃

Keep doing the good job!