Adrien Montagu

Hello @markdoerr, I completed the upload exemple on your branch and is working well. Are you uplaoding back to back or front to back ? The cancelled error may happen...

As discussed we keep otional for PartialUpdate to keep same logic used for the create/update message. If someone reaaly want to have the lookup field of the partial update not...

Note that for now we can't add our own cardinality in the serializers fields. The optional is set from the allow_null argument of the field and the repeated when using...

Hello @markdoerr You may want to look at this issue: https://github.com/socotecio/django-socio-grpc/issues/241 and this documentation: https://django-socio-grpc.readthedocs.io/en/stable/features/grpc-action.html#use-request-and-response-list Also the gRPC size limits is configurable in https://django-socio-grpc.readthedocs.io/en/stable/settings.html#server-options

If I remember correctly the main issue is that bigger message will have impact on your network flow and may increase delay on all your API. But not sure of...

The first part of this issue is completed. The second part is to precisely detailled the filters and pagination fields names and types instead of using a struct. This improvement...

PR blocked after discussion. We figured out that having to pass request/response context to the proto field is not the wanted architecture. We should do all the logic before calling...

Hello @armisael We discussed with @legau and we figured out that others option may come in the future and adding them one by one will be not the best. Instead...

Closing as https://github.com/socotecio/django-socio-grpc/pull/288 completed the first need

@markdoerr I do not understand why you need to do as much to make it work. Just importing the service from your library and register only the ones you want...