-
Notifications
You must be signed in to change notification settings - Fork 440
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
chore(typegen): trace overloadClientMethods usage #7326
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
Component Testing Report Updated Aug 6, 2024 12:17 PM (UTC)
|
config: { | ||
overloadClientMethods: boolean | ||
} |
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.
Event properties should ideally not be nested. Is it OK to flatten the object by removing the config
property and moving overloadClientMethods
out?
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.
Sure. I made it nested since that's how it is here https://github.com/sanity-io/sanity/blob/next/packages/%40sanity/cli/src/__telemetry__/cli.telemetry.ts#L18-L22
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.
But can update
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.
See comment on event properties
fa68585
to
14c9caf
Compare
Description
Trace overload client methods usage
What to review
Is the interface ok for consumption in aplitude/bigquery?
Testing
n/a
Notes for release
n/a no notes needed