In the vscode-debugprotocol package, the type declarations for the ProtocolMessage subclasses, Request, Event, Response, etc. don't specify the type field. ProtocolMessage.type is defined as type: 'request' | 'response' | 'event' | string at the ProtocolMessage level. If the type enum was specified on each subclass as request, response, ect, then TypeScript can automatically cast a ProtocolMessage to the respective subclass when you check the type field, which would save boilerplate.
Similar type declarations could also be used on the Event.event field and Event's subclasses.
In the
vscode-debugprotocolpackage, the type declarations for theProtocolMessagesubclasses,Request,Event,Response, etc. don't specify thetypefield.ProtocolMessage.typeis defined astype: 'request' | 'response' | 'event' | stringat theProtocolMessagelevel. If thetypeenum was specified on each subclass asrequest,response, ect, then TypeScript can automatically cast aProtocolMessageto the respective subclass when you check thetypefield, which would save boilerplate.Similar type declarations could also be used on the
Event.eventfield andEvent's subclasses.