-
Notifications
You must be signed in to change notification settings - Fork 82
[FSSDK-8651] added support for user agent parser for odp #854
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
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.
Just some thoughts otherwise LGTM.
|
||
import { UserAgentInfo } from "./user_agent_info"; | ||
|
||
export interface IUserAgentParser { |
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.
Wondering if we care much about this parser. What about let them inject userAgentInfo as an object or make it more general as "clientOdpInfo" letting them add beyond the user-agent info?
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.
Yeah, we can rename the interface and add a general map<string, unknown> in the UserAgentInfo type.
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.
A question is while we can make it flexible, we may want to pre-define a few "required" names like os-name, os-version, device-model, ... to be consistent with other SDKs. @raju-opti
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.
Yeah. UserAgentInfo type already has os and device fields. We can add a few more.
Summary
Test plan
Issues