Summary

Previously I relied on a database served by third-party restdb dot io. now that the main branch relies on my FastAPI server, it increases the barrier to entry to work on this project. Any contributors must not only run the frontend, but also startup the backend server.

This is not ideal, since it requires that they have knowledge of the existence of that project, and the tools necessary to run it (poetry, python).

Task

• Find a suitable configuration which will allow people to easily host the app: Docker? AWS? AWS Lambda?

Summary

Update service and model set to support the FastAPI server

Tasks

• Update service calls to hit server
• Update models to ensure matching data for server

Discard should redirect back to Home, currently doesn't

Summary

Navbar should update to include a Back Arrow on the top left corner when user is in either Add or Detail pages. Clicking the 'Issue Tracker' text already routes back to home, but the arrow will make it more clearly an option.

Summary

CreateIssuePage.tsx
Intended behavior is for user to be able to stay on the page if the
select the "Create and Add Another" button, but be redirected to Home
when "Create" is selected.

Previous Attempt

I was looking into accessing the .submitter property on the SubmitEvent.
This was problematic since it seemed like TS was expecting a FormEvent instead.

Suggestion

I think a simpler and cleaner strategy will be to add a state variable shouldGoHome.
This variable would also be useful for the "Discard" button.

Also remove the mess from the previous attempt ... 🤢

Summary

Issue Detail basically just copied code from the Issue component. Create a distinct view with editable text for description and assignee.

currently main branch is linked to FastAPI service, but thst requires access to that repo. update main to point to a stable restdbio version until the backend is properly deployed.