Problem description
Commonalities dictate to use PascalCase for Objects naming
Expected behavior
Multiple schema names are not following the PascalCase convention (in webrtc-registration.yaml):
regSessionRequest → should be RegSessionRequest
regSessionResponse → should be RegSessionResponse
regSessionUpdate → should be RegSessionUpdate
Maybe as well the following ones, but that's questionable:
WrtcSDPDescriptor → should be WrtcSdpDescriptor (in both webrtc-call-handling and webrtc-events)
HTTPSubscriptionRequest → should be HttpSubscriptionRequest
HTTPSubscriptionResponse → should be HttpSubscriptionResponse
HTTPSettings → should be HttpSettings
Alternative solution
n/a
Additional context
Release review #105
Problem description
Commonalities dictate to use PascalCase for Objects naming
Expected behavior
Multiple schema names are not following the PascalCase convention (in webrtc-registration.yaml):
regSessionRequest→ should beRegSessionRequestregSessionResponse→ should beRegSessionResponseregSessionUpdate→ should beRegSessionUpdateMaybe as well the following ones, but that's questionable:
WrtcSDPDescriptor→ should beWrtcSdpDescriptor(in both webrtc-call-handling and webrtc-events)HTTPSubscriptionRequest→ should beHttpSubscriptionRequestHTTPSubscriptionResponse→ should beHttpSubscriptionResponseHTTPSettings→ should beHttpSettingsAlternative solution
n/a
Additional context
Release review #105