submit database migration and route #1753
Conversation
There was a problem hiding this comment.
Your database migration script had a fully-qualified reference to the table, which only works in the dev environment, so I could not deploy it as-is. I modified your script slightly and included it in PR #1769 with the exact same file name. I also added a db migration script for the DRUD operations on the project table, but you will still need a new migration script for your Project_Submit stored procedure. I also rebased your branch to a more current version of the develop branch and pushed the commit back up to your PR on github. This didn't really change any of your server-side files, but did merge your client-side files with up-to-date versions from the develop branch. At this point, you should pull the branch 1704-web-api-for-submitting-project down from github and continue working on it. This branch compiles and runs on my local machine, but your new endpoint is missing the stored procedure Project_Submit, and I didn't check what parts of the Submit features work on the front-end.
Partially Fixes # 1704
What changes did you make?
Why did you make the changes (we will use this info to test)?
Issue-Specific User Account
tdm@hackforla.org account was used for this issue.
Screenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)
No visual changes, only code.