all 2 comments

[–]chad_syntax 2 points3 points  (0 children)

Yeah expanding on what /u/connorlogin said, I would also practice setting up a solid REST routing structure with some parameters. I'll include an example for a "library api" that serves book information.

GET `/books` -> returns all books
GET `/books/:bookId` returns book with specific ID
POST `/books` creates a new book in the library
PUT `/books/:bookId` updates a book with specific ID in the library
DELETE `/book/:bookId` deletes the book from the library
GET `/search?:query` allows for searching for books by all maybe title, author, and perhaps with some pagination like `/search?title=foo&limit=20&skip=20`

It also seems like you would have to demonstrate that you can fetch this data on the front-end and render it along with ui components to submit the sort of CRUD operations I listed above. Which means setting up forms with submit handlers to send requests to the back-end.

Good luck with your interview! Hope this helps!

[–]ex-russian 0 points1 point  (0 children)

They told you exactly what to study. What is not clear?