What if protoc-gen-mavsdk made a new major release?

[JonasVautherin]

I am thinking about releasing a v2 of protoc-gen-mavsdk that would break compatibility. Not a huge change, but the existing templates would have to be updated.

This is needed for supporting a new language. I don't see a need for MAVSDK-Go to update to protoc-gen-mavsdk v2 in the near future.

How much would a v2 release of protoc-gen-mavsdk disrupt MAVSDK-Go? I don't see the version being fixed in the generation scripts. Could we try to make the script explicitly pull the latest protoc-gen-mavsdk v1.*? Or add to the README that it requires v1.*?

What do you think?

Just trying to prepare a transition in a way that won't disrupt you 😊.

[JonasVautherin]

protoc-gen-mavsdk v2 is out. I have two examples where I updated the templates to work with it: in Java and in Python.

It's really around the type_info and return_type of non-primitive types: they now return a NameParser instead of returning the formatted type.

I made the changes in a few languages and it was not too hard. It should be possible to update the templates such that generating the code with protoc-gen-mavsdk v2 does not change the sources at all (as compared to the older templates with protoc-gen-mavsdk v1).

Let me know if you have questions! 😊