Andrea Peruffo

> It's a valuable option, but it is still constrained by type checking when parsed into the model during CRD generation. I like it, as the code to handle it...

> Ultimately, the CRD schema will either be rejected or it will not validate as expected As far as I can tell, in this repo, we have always attempted to...

> It's the same whether using a literal JSON/YAML schema in an annotation or typed properties, no? That's accurate, it boils down to the expectations we settle, this is my...

@manusa this should be ready for a final review/merge, possibly, before it gets conflicts.

cc. @EricWittmann @paoloantinori

> I'm happy to see another kiota client in kiota too, full circle 🥳 Yup! Super nice :-) Have you considered shipping Kiota as a Source Generator library? In this...

> This is why the first part of the recommendation is to use the same exact dependencies versions that were shared by the kiota info of the same version of...

> [We already have a script that updates the dependencies for the info command on every release](https://github.com/microsoft/kiota/blob/main/scripts/update-versions.ps1). Is that what you were suggesting? Yup 👍 , unfortunately, it won't work...

> kiota 1.7.0 up to kiota 1.7.9999999 would document needing abstraction 1.5.X instead of 1.5.0, and people would add it with a range (in case of dotnet [1.5.0,1.6.0) javascript 1.5.X,...

I don't understand how it can't work with Go, from what I understand there is not such a limitation and branches and tags are fully supported: https://stackoverflow.com/a/42766877/7898052 and: https://labix.org/gopkg.in Can...