feat(specs): update try transformation specs for no-code

[mehmetaligok]

🧭 What and Why

A follow-up to #4901.

This PR adds no-code transformations support to the try endpoint specs.

Changes included:

• The try endpoint spec is updated.

[algolia-bot]

✔️ Code generated!

Name	Link
🪓 Triggered by	04df79b8d3510c850205a2a3d805393ccb4014da
🍃 Generated commit	911a0c03b7e466bd7a1f68e00cef8a3720d43252
🌲 Generated branch	generated/feat/update-try-transformation-specs-for-no-code

📊 Benchmark results

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

Language	Req/s
go	1752
javascript	1659
php	1516
csharp	1392
python	1077
java	1024
ruby	784
swift	373
scala	23

[Fluf22]

I don't think we should require them here
We could create another object where it's required, but here, it would be a bc I think

[mehmetaligok]

Sorry, I didn't get it.

The code field was previously required; now, instead of the code field, we want to use type and input. So that is why I made them required, because the endpoint wouldn't work without them.

[Fluf22]

Yes, but if people use this prop in their code, it will not work anymore.
For example, if you have this in your JS code:

const transformation: Transformation = { code: '' }

Typescript will be yelling at you because you don't implement type and input, when you'll upgrade to the latest version

[millotp]

it still works with the legacy payload right ? @Fluf22 is right, this is a breaking change if you put them as required

[millotp]

I sent my message without seeing your second one thomas

[mehmetaligok]

Okay. I didnt aware of this will effect and break the generated code. Btw, this is also the case for create payload so I need to revert that change.

But what is the recommendation in here? Make nothing required?

(The api supports legacy payload and the new payload at the same time. So there is no breaking change in the actual API.)

[Fluf22]

@millotp I'd suggest creating a second payload and using a oneOf?
But maybe this would be bc in some languages?

[Fluf22]

Only other option is to make nothing required, yes

[millotp]

having a oneOf is breaking too, I would suggest making everything optional for now, and in a month or so, make the new payload required and leave code as optional.
We don't have a lot of way to deal with breaking changes because of the SLA...

[mehmetaligok]

updated with fa35a7b