Skip to content

fix: use the default value for a rich parameter if unset #6715

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Mar 22, 2023
Merged

fix: use the default value for a rich parameter if unset #6715

merged 2 commits into from
Mar 22, 2023

Conversation

kylecarbs
Copy link
Member

This fixes an error thrown on the workspace settings page when a new parameter is added and the workspace hasn't been built yet.

@kylecarbs
fix: use the default value for a rich parameter if unset
434b912 
This fixes an error thrown on the workspace settings page when
a new parameter is added and the workspace hasn't been built yet.
@kylecarbs kylecarbs requested a review from BrunoQuaresma March 21, 2023 23:16
@kylecarbs kylecarbs self-assigned this Mar 21, 2023
@bpmct bpmct enabled auto-merge (squash) March 21, 2023 23:18
@kylecarbs kylecarbs force-pushed the newparamfix branch 4 times, most recently from aa2782b to f58607f Compare March 21, 2023 23:50
@bpmct bpmct merged commit 38d278a into main Mar 22, 2023
@bpmct bpmct deleted the newparamfix branch March 22, 2023 00:02
@github-actions github-actions bot locked and limited conversation to collaborators Mar 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@BrunoQuaresma BrunoQuaresma BrunoQuaresma approved these changes

@bpmct bpmct bpmct approved these changes

Assignees

@kylecarbs kylecarbs

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@kylecarbs @BrunoQuaresma @bpmct