Léni

fix E203 false positive in list slices

12

Resolves #373

feat: on multiple events accept array

1

Hi, The type definition for `Joystick.on` and `JoystickManager.on` accepts arrays of events or only one event as a string. However this is not the case for the real `on` function...

Use proto-schema-parser library

1

This [library](https://github.com/recap-build/proto-schema-parser) could replace all of our proto parsing/generation logic

Generated PartialUpdate and Response protos should not have pk as optional

1

When generating protos with a PartialUpdate we get : ```proto message SomethingPartialUpdateRequest { optional string uuid = 1; ... } message SomethingResponse { optional string uuid = 1; ... }...

To behave more closely to DRF, we should have our own `get_object_or_404` returning a `NotFound` exception. For now it is caught in [`Service.get_object`](https://github.com/socotecio/django-socio-grpc/blob/master/django_socio_grpc/generics.py#L107).

Error message : ``` django_socio_grpc.exceptions.ProtobufGenerationException: Error on protobuf generation on model None on app testgrpc: Check fail ! Generated proto mismatch ```

We use some soon to be deprecated functions to mark and check if a function is async https://github.com/python/cpython/issues/94912 asgiref addressed this by exposing new functions https://github.com/django/asgiref/tree/main/asgiref/sync.py#L62

Something similar to DRF APITestCase

Model properties should be type annotated with expected return value

Allow writing custom proto messages in generated files

2

Currently the whole file is overwritten, there could be a commented keyword to keep existing messages