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
Timob 13359 part 2 #4091
Timob 13359 part 2 #4091
Conversation
…e other than string.
…if 'reportSuccess' is false for third party events.
…er, success is always boolean, and that they're always tied.
The iOS part looks good. CR -ed for iOS and accepted_ |
code = codeValue; | ||
krollData.remove(TiC.PROPERTY_SUCCESS); | ||
krollData.remove(TiC.PROPERTY_CODE); | ||
} |
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.
What was the behavior before the fix? Could it have been an object like the 'error' property? If so, maybe we should log a deprecation warning like we do for that.
Before the original error handling is that we didn't care. There was no type for success or code enforced or checked. Not sure this is a deprecation, as we can always check and compensate. |
Ran basic sanity check with KS . nothing crashed.. |
Code reviewed and functionally tested. Request Accepted. |
Allow for success and code to be anything and not affect error.