Visitation Flow

[rodrigotiscareno]

Notion ticket link

Visitation Flow

Implementation description

• Created a VisitDTO Class to support incoming data from the front-end.
• Supported data processing to the database for complete data saving.

Steps to test

1. Front-end form values should be recorded in the database for the visitations page
2. Data should be in the specified format.

What should reviewers focus on?

• We made some tweaks as to how the data is entered in the front-end which may need reviewing, perhaps as a separate ticket.

Checklist

• [ x] My PR name is descriptive and in imperative tense
• [ x] My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
• I have run the appropriate linter(s)
• I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

[rodrigotiscareno]

I've left this as a TODO because we need to retrieve the child options from an endpoint. I'd be happy to work on this as part of a smaller ticket.

[github-actions]

Visit the preview URL for this PR (updated for commit 83d3662):

https://childrens-aid-society--pr247-rt-visit-backend-rlo9ghck.web.app

_{(expires Sun, 18 Aug 2024 18:20:02 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 93f6cb7bff946a1edd29d684408e6d31442cf0b1}

[rodrigotiscareno]

Same applied for Transportation, original values were "options={["Full", "Partial", "Unsupervised"]}". We may need to tweak these default options. For now left as generic 1,2,3 until we decide.