Allow saving and updating of intake drafts #77
Merged
Conversation
This file contains 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
Coverage Report (Application)
|
Coverage Report (Frontend)
|
kyle1morel
force-pushed
the
feature/intake-form-draft
branch
from
33ef9b4 to
13294e5
Compare
Bug noticed by navs where backspacing caused the whitespace to be removed automatically
Slipstream update
| housing = { | ||
| projectName: data.housing.projectName, | ||
| projectDescription: data.housing.projectDescription, | ||
| //singleFamilySelected: true, // not necessary to save - check if singleFamilyUnits not null |
There was a problem hiding this comment.
consider getting rid of comments if not required.
sanjaytkbabu
approved these changes
May 17, 2024
wilwong89
approved these changes
May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Improves the current SHAS intake form to allow the saving and updating of draft versions of the form.
Types of changes
New feature (non-breaking change which adds functionality)
Checklist
Further comments