Skip to content
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

Prevent default values from being rendered for refined fields #1487

Merged
merged 2 commits into from
Apr 17, 2024

Conversation

Baccata
Copy link
Contributor

@Baccata Baccata commented Apr 12, 2024

Fixes a bug that would happen when a refinement trait would be used on a member rather than a top-level shape, that would allow for default values of the wrong type to be rendered for the case class field.

This corrects the behaviour by preventing the rendering of default values altogether for case-class fields that are refined

PR Checklist (not all items are relevant to all PRs)

  • Added bootstrapped code
  • Updated changelog

Fixes a bug that would happen when a refinement trait would be used
on a member rather than a top-level shape, that would allow for default
values of the wrong type to be rendered for the case class field.

This corrects the behaviour by preventing the rendering of default values
altogether for case-class fields that are refined
@kubukoz kubukoz merged commit 4295aa0 into series/0.18 Apr 17, 2024
11 checks passed
@kubukoz kubukoz deleted the fix-refined-fields-with-defaults branch April 17, 2024 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants