Releases: cap-js-community/websocket
Releases · cap-js-community/websocket
v1.7.1
v1.7.0
v1.6.4
v1.6.3
v1.6.2
v1.6.1
Fixed:
- Split variadic parameter
context
ofwsContext
intocontext
for single andcontexts
for multiple contexts - Register
ws
protocols in CDS env instead ofcds-plugin.js
- Fix
wsDisconnect
operation without reason parameter - Document
wsDisconnect
with reason parameter - Improve Redis connection check logging
v1.6.0
Fixed:
- Check authorization and service path before websocket upgrade
- Reject connection to non-websocket protocol paths
- Support unauthenticated requests via option
cds.requires.auth.restrict_all_services: false
- Support privileged user, e.g. via
dummy
auth strategy - Fix call to
wsDisconnect
operation without reason parameter - Cast reason parameter for
wsDisconnect
operation to string - Fill
baseUrl
for websocket requests (necessary for request context specific model in toggle/extensibility scenario) - Clean websocket context from internal read-only attributes
- Normalize client identifier on upgrade request
request.id
- Return 404 when url cannot be associated with a service in upgrade request
- Parse string values according to operation parameter type in custom formats (e.g.
pcp
)
Added:
reset
all contexts viawsContext
flagreset: true
- Support multiple contexts in
wsContext
with array value forcontext
- Document usage of
srv.tx(req).emit
for tenant and user propagation in WS broadcasting - Document usage of
wsContext
for formatpcp
andcloudevents