Skip to content

Fix coercing default values on schema generation #35

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 1 commit into from
Jan 13, 2022

Conversation

no1seman
Copy link

Before this patch:

  • defaultValue were not saved on inputObject creation
  • on schema generation defaultValue were not propagated

[x] Tests

@Totktonada
Copy link
Member

We discussed the questions with Yaroslav in voice and he'll return back with updates/clarification.

@DifferentialOrange
Copy link
Member

DifferentialOrange commented Jan 11, 2022

Well, since there are some changes planned, I will not review the current version and wait for the update

@no1seman no1seman force-pushed the fix_defaults_coerce branch from 423886e to f7b11a2 Compare January 12, 2022 17:14
@no1seman no1seman requested a review from Totktonada January 12, 2022 18:52
Copy link
Member

@Totktonada Totktonada left a comment

Choose a reason for hiding this comment

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

No objections from me.

Copy link
Member

@DifferentialOrange DifferentialOrange left a comment

Choose a reason for hiding this comment

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

Well, the PR definitely does what it intends to do.

It is a bit unsatisfying that defaultValues are still seems to be broken after this PR, but it seems like the feature is not that highly demanded and it will be processed as a part of standard working pipeline. I added a ticket to backlog, its priority may be changed if someone will request it, see #37

@Totktonada Totktonada merged commit 2860f78 into master Jan 13, 2022
@Totktonada Totktonada deleted the fix_defaults_coerce branch January 13, 2022 14:47
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.

3 participants