🐛 #192 - Guardian 404

[lprichar]

Issue

Fixes #192

Description

Primarily fixes the 404 errors with fetching guardians as described in the ticket. Additionally:

• Logs stack traces on error for affected requests
• Removes the memory repository, it doesn't work
• Defaults make start to use the local repository
• Default debugging in VSCode to use local storage (for simplicity for new devs)
• Adds documentation on how to debug in Windows
• Fixes minor unrelated issues with Postman

This PR felt sufficiently small that I thought it would be ok to fit in the prior 6 small issues into one PR rather than creating a bunch of issues, but I can break out into separate PR's if desired.

Testing

1. POST to {{guardian-url}}/api/{{version}}/guardian with "guardian_id": "guardian_1" to create a guardian
2. GET {{guardian-url}}/api/{{version}}/guardian?guardian_id=guardian_1

It should now return a 200

[lgtm-com[bot]]

This pull request introduces 1 alert when merging e6223fe3d51ea7b5643cb4225c069028cdabc629 into ff32ddfc184585e586f935c0d24c340fb64e6dd5 - view on LGTM.com

new alerts:

• 1 for Unused import