This repository was archived by the owner on Oct 29, 2024. It is now read-only.
Fixing wrong parameter order on configureWithTimeout function on Android #193
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requirements
Related issues
Lmk if you need an issue created for this.
Describe the solution you've provided
Changed the order of the params in the
configureWithTimeout
function as it wasn't matching the order on the JS and the iOS side.Correct order (iOS & JS):
config
context
timeout
isContext
Incorrect order (Android):
config
context
isContext
timeout
Describe alternatives you've considered
Tried to fix this on the JS side first, but then noticed that iOS and JS is in alignment so I only updated Android.
Additional context
Repro: invoke
configure
with a timeout set. Example:await client.configure(config, user, 60);