takenoteinc / takenotes Goto Github PK

Since DB now has only one table, will need update the diagram to reflect new structure.
Also remove elasticsearch.

Notes interface at the home page.

Create PUT request for notes at {base_url}/users/{id}/notes/{notes_id}. This endpoint will be used to update the users notes. Input should be a note object, output/response can be the updated user object.

GET
/users/{user_id}/weeks

Gets all weeks for a user.

Need to add a POST request to our main endpoint. This POST request should route to a handler just for POST requests.

Users should be able to send a POST request to {base_endpoint}/. The request body (input) will contain a brand new JSON User object. The function should add this user into our database and return a 200 on success.

If you decide to do a custom flow - use this https://docs.amplify.aws/lib/auth/start/q/platform/js#configure-your-application and plug in our user pool id from config file

Create POST request for notes at
{base_ur}/users/{id}/notes. This endpoint will be used to create a new note object. Input should be a note object and output will be updated user object.

Need to add a DELETE request to our main endpoint. This DELETE request should route to a handler just for DELETE requests.

Users should be able to send a DELETE request to {base_endpoint}/{id}. The function should delete the User corresponding to {id} and return 200 on success.

Building navigational timeline which will change the state of the app on week selections.

Need to add a GET request to our main endpoint. This GET request should route to a handler just for GET requests.

Users should be able to send a GET request to {base_endpoint}/{id}. The function should grab the User corresponding to the {id} and return it in JSON format. There is no need for input parameters or an input body because we just need to return the entire User object.

Create POST request for entries at
{base_ur}/users/{id}/journal/weeks/{weekIdx}/entries/{entryIdx}. This endpoint will be used to create a new entry object. Input should be a entry object in body under entry property. Output will be new item under data field and id field in response will be id of new entry to put in dataset.

Notes should have id's to prevent over writing the entire notes body everytime we update one note. Also as a result we should support CRUD at note level.

The focus for now - to add id on put request.
The notes field in DB will be a map and the id
will be used to index the map. The value associated with the ID key will be a note object with an id field holding the key and a header and content field representing the note.

Create DELETE request for notes at {base_url}/users/{id}/notes/{notes_id}. This is to allow a user to delete a note. Input should be nothing and output will be the old userObject?

PUT
/entries/{entry_id}
Takes in an entry and an entry id and updates it.

Update template to trigger post User endpoint on post confirmation event from cognito. Update naming of resources to ref stage parameter.

Create PUT request for journal at {base_url}/users/{id}/journal. This endpoint will be used to update the users journal. Input should be a journal object, output/response can be the updated user object.

Create PUT request for weeks at {base_url}/users/{id}/journal/weeks/{weekIdx}. This endpoint will be used to update a specific week in the users journal. Input should be a week object, output/response can be the updated user object.

We want to push common code into lambda layer.

Convert JSON response structures to be standard across all routes. Currently some have the user doc on data.data.Attributes and some send back with user on data.Item

i.e

{
data: { updatedUserObject }
}

Update handler to delete the user in cognito user pool.

If/when the POST errors, return a 400 with a body containing a list of the invalid inputs. i.e.

{
  ["startDate", "endDate", "name"]
}

GET
/entries/all/{week_id}

Gets all entries for a given week.

Document what each line means
Add tags where we need to change or update stuff

Create DELETE request for entries at {base_url}/users/{id}/journal/weeks/{weekIdx}/entries/{entryIdx}. This endpoint will be used to delete the users entry given ID. Input should be a entry id, output/response will be the old user object.

Need to add a PUT request to our main endpoint. This PUT request should route to a handler just for PUT requests.

Users should be able to send a PUT request to {base_endpoint}/{user_id}, the input request body should be the entire User object, and should overwrite the User object in our database. Essentially updating the User.

Access token is currently grabbed from the request body, move this to be grabbed from header instead.

Change deleteUser code to grab it from header, and change front end code to send it in header.