[REQ] Add documentation for each server stub generator about how to use it
Created by: mohamnag
Is your feature request related to a problem? Please describe.
I just found this project and as a new user it took me a lot of time to find out how the generated code (for server stubs) is supposed to be used.
For example I was interested in two generators spring and kotlin-spring. One is generating controller classes that have additional methods which can easily be overwritten in a subclass and implemented. It is not even necessary to include the generated sources in the project and they can be included as a dependency.
The kotlin-spring one, on the other hand, generates controllers that should be included as source and updated directly.
Even for two generators which are pretty much similar, it was hard to find out a best solution and even those may not be the way developers of the generators meant to be used. This can cause other problems when future changes breaks the way generator is used and at some point might defy the reason this generator is used (which is saving time).
Describe the solution you'd like
It would be nice if each generator described in its documentation not only the options it is providing but also how the generated code is supposed to be used.
Describe alternatives you've considered
none?!