docs(abtests) v3 api

[Niamsy]

🧭 What and Why

🎟 JIRA Ticket: OPTIM-1443
OPTIM-1456
OPTIM-1535

Changes included:

• ADD abtests-v3 specs openapi
• POST /3/abtests allows more than 2 variants, a configuration, and requires a set of metrics to be retrieved during the A/B Test
• GET /3/abtests returns all the metrics requested during A/B test creation
• GET /3/abtests/{id} idem

🧪 Test

[algolia-bot]

✔️ Code generated!

Name	Link
🪓 Triggered by	5366c01727199e9311554f4dffe61b22ad21fc37
🍃 Generated commit	887e639152b44884f35dad20727296e864561677
🌲 Generated branch	generated/docs/abtests/api-v3

📊 Benchmark results

Benchmarks performed on the method using a mock server, the results might not reflect the real-world performance.

Language	Req/s
javascript	1672
go	1601
php	1500
csharp	1304
java	1088
python	1079
ruby	850
swift	848
scala	23

[cdhawke]

I did a first pass - we can make adjustments after we get a base established too!

[millotp]

Hello @Niamsy, this is the first time that we have a new api version in the repo, how would like it to distribute it ?
Are you planning on supporting v2 as well ?
Do you want v3 to be in a different package on npm or just change the version of the existing one ?

[Niamsy]

Hello @millotp, we're planning to support both v2 and v3 in parallel. As for the distribution, I'm not sure, maybe @cdhawke has a better idea.
We're still in the development phase for the v3 api but we wanted to have an openApi spec somewhere so that's why there is this PR, but we're not planning on merging it right away

[cdhawke]

@millotp - you might know better how to separate these. We will support both versions, and the only thing changing outside of the request signatures/objects will be the /2 -> /3 in the url used to differentiate the version. Would you recommend keeping it separate? We might in the future try to transition off of v2, but there's no official timeline for that, as it will entail an EOL process. In this future scenario would it be better to have it as a separate package?

[Niamsy]

Hi @millotp, we'll soon want to release abtests v3 and merge this PR. As mentioned previously, we will support both v2 and v3 in parallel. Can we just merge this PR when we're ready or do we need to do specific things before ?

[shortcuts]

wonderful

[shortcuts]

Suggested change

description: No A/B tests are configured for this application.

it will just represent the nullable attribute in the doc/clients, no descriptions are expected