Skip to content

fix: prevent change in defaults if user unsets in template edit #10793

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.

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

Merged
merged 3 commits into from
Nov 21, 2023

Conversation

Emyrk
Copy link
Member

@Emyrk Emyrk commented Nov 20, 2023

If we used *string in api update fields instead of string we could use the nil then this would not be necessary. It would require a bit of an overhaul on many of our api fields 😢

@Emyrk Emyrk changed the title fix: template edit not change defaults if user unset fix: prevent change in defaults if user unsets in template edit Nov 20, 2023
johnstcn
johnstcn previously approved these changes Nov 20, 2023
Copy link
Member

@johnstcn johnstcn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I vaguely recall thinking "I should probably make these pointers like in v1", but I can't remember why I decided against it :(

@johnstcn johnstcn dismissed their stale review November 20, 2023 15:40

just saw that tests are broke :(

@Emyrk
Copy link
Member Author

Emyrk commented Nov 20, 2023

just saw that tests are broke :(

Oooof. Will fix.

@Emyrk Emyrk merged commit 7060069 into main Nov 21, 2023
@Emyrk Emyrk deleted the stevenmasley/template_edit_unset branch November 21, 2023 00:14
@github-actions github-actions bot locked and limited conversation to collaborators Nov 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants