help you fix your problem There is no way to accomplish this today. The build system, build_runner does not allow overwriting files so it isn't possible to programmatically insert these annotations into the protobuf generated code. This would require either an option in the protobuf generator to change the serialization format, or another serialization framework built on top of protobuf that would understand their source and can generate the custom serialization required.
hop of those help? Not quite what you're looking for but you could use API Viz which automatically produces UML like diagrams from class hierarchies and can be augmented with doclet tags. You'd have to mark up your classes a little, but it's a great tool and worth using wherever you're trying to visualise large or complex projects.
will be helpful for those in need You have to think of models as representations of your database. You don't want to dynamically create tables in your database. It needs consistent structure for sanity's sake. That said, what you are describing can be done with related models. For example, a structure like this will allow you to add as many teams as you'd like:
team_name = ...
# Whatever other attributes.
first_name = ...
last_name = ...
# Assign players to a team.
team = models.ForeignKey(Team)
# Whatever stats you want to keep on the players
Automatically document @PathVariable annotated parameters within @ModelAttribute annotated methods
help you fix your problem This is certainly possible. Model attributes on methods are not supported currently. Instead, you could take the following approach. Mark the getTenant method with an @ApiIgnore (not sure if it gets treated as a request mapping.) In your docket you can add tenantKey global path variable (to all end points). Since this is a multi-tenant app it's assuming this applies to all endpoints.
How is @ConfigurationProperties-annotated classes detected automatically with @SpringBootApplication Annotation