We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Following is how equals has been implemented for TokenDetails
equals
TokenDetails
@Override public boolean equals(Object obj) { TokenDetails details = (TokenDetails)obj; return equalNullableStrings(this.token, details.token) & equalNullableStrings(this.capability, details.capability) & equalNullableStrings(this.clientId, details.clientId) & (this.issued == details.issued) & (this.expires == details.expires); }
This implementation doesn't take into account when obj is null or not the type of token details.
Expected Return false when obj is null or a different type
Spotted: Flutter plugin Stream writer does this check when writing types to streams
protected void writeValue(@NonNull ByteArrayOutputStream stream, @Nullable Object value) { if (value == null || value.equals(null)) { stream.write(NULL);
The text was updated successfully, but these errors were encountered:
➤ Automation for Jira commented:
The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3465
Sorry, something went wrong.
ikbalkaya
Successfully merging a pull request may close this issue.
Following is how
equals
has been implemented forTokenDetails
This implementation doesn't take into account when obj is null or not the type of token details.
Expected
Return false when obj is null or a different type
Spotted:
Flutter plugin Stream writer does this check when writing types to streams
The text was updated successfully, but these errors were encountered: