Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
cmsc388Bwinter2022-student
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Andrej Rasevic
cmsc388Bwinter2022-student
Commits
39ac08cc
Commit
39ac08cc
authored
3 years ago
by
Andrej Rasevic
Browse files
Options
Downloads
Patches
Plain Diff
more updates
parent
591ebd43
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
exercises/exercise3/InMemoryApi/routes/api/v1/contacts.js
+3
-2
3 additions, 2 deletions
exercises/exercise3/InMemoryApi/routes/api/v1/contacts.js
with
3 additions
and
2 deletions
exercises/exercise3/InMemoryApi/routes/api/v1/contacts.js
+
3
−
2
View file @
39ac08cc
...
...
@@ -6,7 +6,7 @@ You will need to define the following routes:
contacts in your application and a response code of 200
2) POST: it will respond to a POST request that will generate a
new instance of a contact and add it to the in memory collection
and a response code 201
and a response code 201
and a message saying "successfully added contact".
2) /api/v1/contacts/:id
This route will need to responde to 4 requests:
1) GET: it will respond with the serialized form of the requested
...
...
@@ -21,12 +21,13 @@ You will need to define the following routes:
conditions, e.g. if you are passing values for both the firstName and lastName then
your matches need to match both query parameters. Note: query params end at the end of the route,
and all come after the ? character and are combined with a &.
/api/v1/contacts/:id
3) PUT: it will update the resource with the information attached in
the req.body property.
Your route should respond with a 201 response code along with the updated
resource otherwise 404 with an error message of "unable to update resource".
4) DELETE: it will remove the contact from the collection with the matching id
in the request.params object and respond with a status code of 201 alon
e
with
in the request.params object and respond with a status code of 201 alon
g
with
the deleted resource in the response. If the resource is not found the route should
respond with a 404 error and message "resource not found".
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment