fix(fields): fix issue with nil params in date-related functions [CLK-509330] #31
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Flexicon
approved these changes
Nov 21, 2024
nikitaclicks
approved these changes
Nov 21, 2024
szygendab
approved these changes
Nov 21, 2024
better function name Co-authored-by: Nikita Dmitriev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The formula date functions do not handle null/undefined/false/'' values gracefully, requires to pass a valid date. In such conditions we don't want to error out, just return
Number.NaNas a result (this is treated by the FE as a "no-value" value).Tests
Screen.Recording.2024-11-20.at.17.24.12.mov