-
Notifications
You must be signed in to change notification settings - Fork 22
fix(specs): abtest v3 naming conflict with Metric type #5090
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
💥 Breaking changes detected !!Either this PR or a previous PR not released yet introduced breaking changes, be careful when merging. ✔️ Code generated!
📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
@cdhawke does the generation looks correct here? |
@shortcuts - no, looks like it was still reusing one of the names inadvertently. I'm trying to give them distinct names to map better and avoid the collisions. let's see after this next run |
@shortcuts I think it looks okay now... |
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.
LGTM
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.
indeed good catch!
…ated) [skip ci] Co-authored-by: Christopher Hawke <[email protected]> Co-authored-by: Clément Vannicatte <[email protected]>
algolia/api-clients-automation#5090 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Christopher Hawke <[email protected]> Co-authored-by: Clément Vannicatte <[email protected]>
🧭 What and Why
The typescript types being generated for the v3 abtesting client don't match the object definitions in the openapi spec file. We think this is due to a naming collision when generating the types -
Metric
is defined elsewhere and being reused improperly.Changes included:
🧪 Test
N/A