Issue Tracker
- Prevent cross-site scripting (XSS) attacks.
- I can POST
/api/issues/{projectname}
with form data containing required issue_title, issue_text, created_by, and optional assigned_to and status_text. - The object saved (and returned) will include all of those fields (blank for optional no input) and also include created_on (date & time), updated_on (date & time), open (boolean, true for open, false for closed), and id.
- I can PUT
/api/issues/{projectname}
with an id and any fields in the object with a value to update said object. Returned will be 'successfully updated' or 'could not update'. This should always update updated_on. If no fields are sent return 'no update field sent'. - I can DELETE
/api/issues/{projectname}
with an id to completely delete an issue. If no id is sent return 'missing id', success: 'successfully deleted', failed: 'could not delete'. - I can GET
/api/issues/{projectname}
for an array of all issues on that specific project with all the information for each issue as was returned when posted. - I can filter my GET request by also passing along any field and value in the query (for example:
/api/issues/{project}?open=false
). I can pass along as many fields and values as I want. - All 14 tests are complete and passing.