-
Notifications
You must be signed in to change notification settings - Fork 480
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
Add RightSideComparisonResult as factResult #396
Conversation
Conceptually this is fine a few things It should be in a field like valueResult not overriding the factResult You should set the field unconditionally Make sure you update the types and please add some more unit tests |
I've followed your advice and added the field unconditionally. Also i've updated all acceptance tests to check for the new value and updated the typings. I've also added an specific test for this feature checking if the valueResult matches. |
I've found that the toJSON Serialization was missing and added it. I've tested in a working application and now it correctly returns the value even when serializing to JSON. |
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.
@thorin8k Looks great, thanks for the contribution!
re-apply changes from #396 onto v8
Hello!
I noticed the issue mentioned in #310, which is important for my use case, so I tried to address it with this pull request.
My implementation approach is straightforward. When setting the factResult for a condition, if the value property is an object, I include the rightSideValue as the factResult.
I'm eager to see this merged, as it is of great interest to me.