protocol-buffers

protobuf.js version: 6.8.8

For enumerations defined in proto3, the switch statement generated by pbjs triggers the eslint warning default-case since there is no default case. This should be added to the list of eslint-disable rules in the header comment of the generated source file.

The less than/greater than checks should check if the input value is NaN. NaN is defined to not be equal to any other number, and all numerical comparisons yield false. Therefore, if I have a field that's annotated with (for example) (validate.rules).double.gt = 0, that field should fail validation if given NaN.

Describe the bug

According to the Using TLS guide, the use of

PlatformSupport.makeEventLoopGroup(loopCount: System.coreCount)

is preferred over calling MultiThreadedEventLoopGroup for TLS. Presumably this is generally true and the Examples should be updated accordingly.

Both the protolock tests and the plugin checks should be fairly straightforward to convert into Actions format.

Once the user defines(and saves) the collection, user can just click a button to test all the requests within that collection at once.
Further discussion needed whether protoman will just check the status code or the actual return(users can decide if they want to)