fix(specs): abtest v3 naming conflict with Metric type#5090
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... |
…ated) [skip ci] Co-authored-by: Christopher Hawke <69921547+cdhawke@users.noreply.github.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#5090 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Christopher Hawke <69921547+cdhawke@users.noreply.github.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
🧭 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 -
Metricis defined elsewhere and being reused improperly.Changes included:
🧪 Test
N/A