-
Notifications
You must be signed in to change notification settings - Fork 8
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
refactor: added browser-info to confirm call #171
Conversation
device_model: option<string>, | ||
os_type: option<string>, | ||
os_version: option<string>, |
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.
can you make the type string instead, anyways from native side you are always collecting these and putting them in hyper params
device_model: option<string>, | |
os_type: option<string>, | |
os_version: option<string>, | |
device_model: string, | |
os_type: string, | |
os_version: string, |
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.
any way both serve the same purpose, right?
device_model: getOptionString(hyperParams, "device_model"), | ||
os_type: getOptionString(hyperParams, "os_type"), | ||
os_version: getOptionString(hyperParams, "os_version"), |
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.
device_model: getOptionString(hyperParams, "device_model"), | |
os_type: getOptionString(hyperParams, "os_type"), | |
os_version: getOptionString(hyperParams, "os_version"), | |
device_model: getString(hyperParams, "device_model", ""), | |
os_type: getString(hyperParams, "os_type", ""), | |
os_version: getString(hyperParams, "os_version", ""), |
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.
do we need these changes @sh-iv-am?
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.
I don't think so as browser_info
is not required for all PMs and connectors.
This PR will browser/ device details to the confirm call