Acceptance criteria

• All e2e tests for the project are passing

Guidance 🧭

Check the e2e-testing guide for steps on how to set up your

Description

When you return all of the videos from the /api/videos endpoint your API should support an optional query parameter that will change the ordering of the data

/?order=asc

and

/?order=desc

Acceptance criteria

• When you receive asc the videos should be returned in ascending order by the number of votes. i.e. starting with the lowest number of votes.
• When you receive desc the videos should be returned in descending order by the number of votes. i.e. starting with the highest number of votes.
• If no parameter is passed, the order should be by ID.
• Users can select an ordering in the frontend

Example

Please check https://lvl499c--cyf-fsa-solution.netlify.app for an example solution of this level

Acceptance criteria

• When a user adds a new video, store the date and time they posted it in the database.
• The date created value is displayed in the frontend

Guidance 🧭

This might require a change to your database schema - you should make sure you can deploy this change without breaking existing videos, the same way the rating system was done.

Example

Check this example implementation to see how this feature could be implemented.