ItineraryFlow state methods

[sonicspeed123]

Description

new State's were added to allow for other flowstates. get_next_state() base functionality was created get_previous_state() base functionality was created visit_state() base functionality was created

current implementation of get_next and get_previous will return the expected state based on the current state in a linear fashion. ex, if the object's current state is updated, get_next will return updated and get_previous will return reserving.

Notes for edge cases: if the current state is login, get_previous will return login if the current state is archived, get_next will return archived

Motivation and Context

Pull request made for issue: https://github.com/heyitsmass/BayView/issues/30

Screenshot:

Additional Notes

currently we return a value of type FlowState in get_next/get_previous_state(), If needed, we can adjust it so that we return an actual State object instead.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [ ] Refactoring (non-breaking change)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [X] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.

Requested Changes:

I'd like to ask if we can add a new potential value for FlowState, that being "null" to allow for our edge cases to refer to those instead of themselves to help avoid confusion.

[vercel[bot]]

Someone is attempting to deploy a commit to the bayview Team on Vercel.

A member of the Team first needs to authorize it.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
bay-view	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 17, 2023 11:13pm