-
Notifications
You must be signed in to change notification settings - Fork 96
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
basetypes: fix equality for values with nil elementType #961
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.
LGTM
Perhaps a bug fix change log entry is warranted?
Thanks @bendbennett - added separate changelog entries for each type. Let me know if you'd prefer a single entry instead! |
@bendbennett / @jar-b anything else need to happen here? Implementation change looks good to me 😄 |
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.
LGTM 🚀
A `MapValue` with a nil `elementType` is an invalid state, and therefore cannot verify equality with another value. This change to the `MapValue.Equal` method now returns `false` if either the receiver or argument have a nil `elementType`.
Apologies, I missed that this needed rebased. Should be ready now! |
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.
Thanks for this @jar-b! 🚀
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
A
MapValue
,ListValue
, orSetValue
with a nilelementType
is an invalid state, and therefore cannot verify equality with another value. These changes to theEqual
method now returnsfalse
if either the receiver or argument have a nilelementType
.Closes #959