-
Notifications
You must be signed in to change notification settings - Fork 31
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
Additional fix for validation of hidden fields in non-repeating groups #82
Conversation
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.
🥇
Remember to bump package.json 🙃
Well, that failing test right after merging #84 was embarrassing... 🙈 I'll look into it again! |
Oh no! 🙃 In my experience, If Jeeva has reported something as a bug it has a tendency to be an actual bug and not a faulty test. It might be worthwhile to investigate if this is actually a weakness in our current code. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
…amp for date picker component (#82) The implementation actually defaults to 'undefined', and there is a strict check if the timestamp is set to 'false'. The result of this check (timestamp === false) will only be true if timestamp is 'false'. 'undefined' (default) will not result in this check evaluating to 'true'.
Description
The last fix (#69) didn't account for the other way to reproduce this issue; by hiding the fields themselves, even though they are defined in a group that could be hidden instead. With this fix both variants work as expected.
Fixes
Verification
Documentation