Organize generated gRPC client

[obrunsmann]

• Publish model files from the library → No imports of the .pb.dart files should be necessary from outside the package
• Remove unused generated files (some unit test files have been generated as well from google/protobuf package)

[Allan-Nava]

How can you handle the grpc stuff ?

[obrunsmann]

What do you mean?

[Allan-Nava]

What do you mean?

Like this for nakama swift https://github.com/Allan-Nava/nakama-swift/tree/master/proto

[obrunsmann]

Hmm unfortunately I haven't quite figured out what you mean yet. This issue is about removing the files that are currently generated but not needed.

Is just clean up - not very critical :)

[Allan-Nava]

Hmm unfortunately I haven't quite figured out what you mean yet. This issue is about removing the files that are currently generated but not needed.

Is just clean up - not very critical :)

Ah ok, because in swift we generated automatically the swift files from proto

[obrunsmann]

Yeah right, doing same here (https://github.com/obrunsmann/flutter_nakama/blob/main/lib/api/generate.sh). But the problem I would like to solve is to organize the mass of generated API Docs for all the compiled pb stuff like here: https://pub.dev/documentation/nakama/latest

So the first thing might be to disable generation of unused pb files and the second thing might be to check if the files could get some namespaceing so that this flutter library not expose so many classes

[Allan-Nava]

Yeah right, doing same here (https://github.com/obrunsmann/flutter_nakama/blob/main/lib/api/generate.sh). But the problem I would like to solve is to organize the mass of generated API Docs for all the compiled pb stuff like here: https://pub.dev/documentation/nakama/latest

So the first thing might be to disable generation of unused pb files and the second thing might be to check if the files could get some namespaceing so that this flutter library not expose so many classes

Ok as you wish