-
Notifications
You must be signed in to change notification settings - Fork 5
Compute defaultValue on client-side #4234
#4238
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
Conversation
|
@anatol-sialitski I've opened a new pull request, #4239, to work on those changes. Once the pull request is ready, I'll request review from you. |
| getDefaultValueFromConfig(): Value; | ||
|
|
||
| getRawDefaultFromConfig(): unknown; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It shouldn't matter where default value is coming from, so I suggest calling it simply getDefaultValue and getRawDefaultValue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not agree. That is a raw value which can be computed later. For instance, for the instant type, we can use a now expression as a default value, and that expression will be computed to an ISO string.
No description provided.