Bug in Exploring Service Mocking: Mocking GET Routes (2)

mutation5252

References to http://localhost:5050/ should instead read http://localhost:3000/.

fcioanca

Hi @mutation5252

Thank you for flagging this. We have reached out to the course author to confirm the change. Once confirmed, we will update the course.

Regards,
Flavia
Linux Foundation Education

ajjones

Hi mutation5252, could you please walk me through the steps you took? When you say the course references port 5050 but should instead say port 3000, are you referring to the mock service or the web app?

mutation5252

@ajjones The mock service runs on port 3000 whereas the web app runs on port 5050. The document states,

The populateProduct function now accepts a category argument and the call to fetch has been updated to:

const res = await fetch(`${API}/${category}`)

Earlier, it defines API to be:

const API = 'http://localhost:3000'

It then indicates:

When a category is selected, a request is made to http://localhost:5050/{cat}, where {cat} is the selected category. So, ultimately we need our mock service to support two routes:

• GET http://localhost:5050/electronics
• GET http://localhost:5050/confectionery

However, since the mock service runs at port 3000, all references to 5050 in the documentation in the lines above should read 3000.

ajjones

Thank you for noticing this mutation5252, good catch! The course will be updated appropriately to reflect this change.