Post request #22
Post request #22
Conversation
| "header": [], | ||
| "body": { | ||
| "mode": "raw", | ||
| "raw": "{\n \"title\":\"Wie Traurig\",\n \"message\":\"Ich habe meinen Freund im Denver verloren und jetzt bin Ich ganz allein :(\",\n \"name\":\"Till Lindemann\",\n \"latitude\":125.456892,\n \"longitude\":-18.982791\n}", |
There was a problem hiding this comment.
Sprichst du deutsch...? I'll be your new friend :)
There was a problem hiding this comment.
Nur ein bisschen.. leide habe Ich viel vergessen 😅
| " pm.expect(attributes['latitude']).not.to.be.null;", | ||
| " pm.expect(attributes['longitude']).not.to.be.null;", | ||
| " pm.expect(attributes['message']).not.to.be.null;", | ||
| " pm.expect(attributes['name']).not.to.be.null;", |
There was a problem hiding this comment.
Should name be included in the post? Just want to clarify so we are sending the correct info to the POST
There was a problem hiding this comment.
Also - is this a required field or is it a field where if the user does not fill it out it will send to the server as anonymous?
There was a problem hiding this comment.
The latter - it is optional and defaults to Anonymous if not provided
| " pm.expect(attributes['name']).not.to.be.null;", | ||
| " pm.expect(attributes['title']).not.to.be.null;", | ||
| " pm.expect(attributes['location']).not.to.be.null;", | ||
| "});" |
There was a problem hiding this comment.
Right now the Object we are sending
looks like
const newStory = {title, message, latitude, longitude}
|
Possibility to revisit in future in case we want JSON response to conform to JSON 1.0 Spec |
Changes Implemented:
api.urls.pyto dry up logic (keepapi/v1namespacing within Django project root vs app module)api.views.pyto useClass-based views(vsFunction-based viewsin prior implementation)Postmansuite to test the implementation of the following:/api/v1/stories(index of all stories, note, still more work to be done here once geoloc API is integrated)/api/v1/stories/<id:pk>(retrieve an individual story)/api/v1/stories(create a new story)/api/v1/stories/<id:pk>(delete an individual story)DevandProdinto postman dir, so you can import both and toggle between the two, for future testing phasesPostmancollection (if any changes made to endpoints that could break tests as currently written).Quality Control Checklist:
Blockers (if applicable): None, but a special thank you to the
Djangodocs for the incorrect tutorial on how to build routes!! 🤦🏽♂️Next Steps & Additional Notes:
PATCH/PUTendpoint to update a storypytestrequest specs (if they exist). Admittedly, have done zero research on this, and have just been using Postman to get our endpoints tested and deployed as quickly as possible for the FE team.