feat: Add material details to list component and schema #3384
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
|
Removed vultr server and associated DNS entries |
|
This will result in changes to material questions data structure (previously split between property. and proposal. and specific to the selected type, e.g. proposal.materials.roof), now appended as .type, .existing, and .proposed separately to (presumably) a counted proposal.materials as the list component data field. |
DafyddLlyr
approved these changes
Jul 8, 2024
|
Thanks @augustlindemer, just merged to staging where it will be live in about 15 mins. There's likely going to be a production deploy later today to sort out some certificates and subdomains so we'll pick this up at the same time 👍 |
|
perfect @DafyddLlyr! |
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.
Added material detail questions to list component and schema