BREAKING CHANGE: strip out the api and database services#117
Merged
Conversation
cjyetman
reviewed
May 28, 2025
Co-authored-by: CJ Yetman <cj@cjyetman.com>
cjyetman
approved these changes
May 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Given the latest approved version of the PRD for this project, it was determined that the database and API services that we had originally envisioned won't be necessary until a later version of the application.
To keep things stream-lined, @AlexAxthelm @cjyetman and myself have decided to focus solely on the React front-end in this repository.
Shortly, we will enable continuous deployment of this React application directly to production, based on the GitFlow branching strategy. This also benefits from us reducing technical debt and overhead that is not immediately useful or required for the deployment or serving of the application.
With that said, given that we do anticipate a future need for a database and API, we have kept the scaffolding of this available in the web-api-poc repository.
Specifially, an identical version of the
apianddbservices, all relevant actions, tests, integration tests,dockerand.envset-up and other related goodies have been preserved in that repository.Relates to RMI/web-api-poc#56