Please describe both what is changing and why this is important. Include:
I Added specific typing for void requests. This is important because first, IDEs usually give warnings when an object's type is not specified. It does not do anything at runtime because of type-erasure, but it makes it impossible for the IDE to know what is supposed to come out of that object.
This causes a small inconvenience when using the library. In my case, I wrapped the auth0 library with custom code that handles Rate-limiting better and automatically execute requests, which is why the dynamic typing is needed.
I was therefore forced to specify myself the Any type (because the library doesn't specify the Void)
Testing
Does not impact tests. It just removes warnings.
[ ] This change adds test coverage
[x] This change has been tested on the latest version of the platform/language or why not
Changes
Please describe both what is changing and why this is important. Include:
I Added specific typing for void requests. This is important because first, IDEs usually give warnings when an object's type is not specified. It does not do anything at runtime because of type-erasure, but it makes it impossible for the IDE to know what is supposed to come out of that object.
This causes a small inconvenience when using the library. In my case, I wrapped the auth0 library with custom code that handles Rate-limiting better and automatically execute requests, which is why the dynamic typing is needed.
I was therefore forced to specify myself the
Anytype (because the library doesn't specify theVoid)Testing
Does not impact tests. It just removes warnings.
Checklist