Fix #

• Payload byte length calculation

Breaking Changes #

• Drop all custom contexts based on lifecycle component
• Create a generic Context interface to replace all custom contexts
• Use new types from revali_router_core

Fixes #

• Issue where allowed headers were not inherited properly
• Issue where allowed headers could block requests with unknown headers

Features #

• Create new add method to MutableCookies
• Add clean up to router close method to prevent memory leaks

Enhancements #

• Check for closed connection before sending response

Enhancements #

• Binary serialization/deserialization

Enhancements #

• Catch errors when sending data over the web socket

Features #

• Create kDebugMode, kProfileMode, and kReleaseMode constants

Fixes #

• Issue where resolving the payload would hang on a web socket message

Features #

• Explicitly check for binary types when resolving body
• Clean up resources after response has been handled
• Support sending data asynchronously
  • As opposed to only on an event received

Enhancements #

• Check for null values in addition to NullBody body data types
• Handle exceptions when resolving body
• Coerce body types when no mime type is provided
• Improve path parameter extraction
• Force sequential execution of sent WebSocket messages

Fixes #

• Issue where crash would occur during SSE when connection was closed by client unexpectedly
• Issue where endpoint path would result in 404 when parent controller's path was empty

Fixes #

• Issue where WebSocket would only send the first message

Features #

• Create WebSocketContext class for context management of WebSocket connections
  • Specifically closeing the connection
• Allow empty paths for parent routes when their handler has not been set

Breaking Changes #

• Remove UnknownBodyData, will default to a ByteStreamBodyData instead
  • UnknownBodyData had the potential to hang if the body was a open stream

Features #

• Create WebSocketContext class for context management of WebSocket connections
  • Specifically closeing the connection
• Allow empty paths for parent routes when their handler has not been set

Features #

• Add support for primitive body types
  • int, double, bool

Enhancements #

• Clean up resources after request is complete

Fixes #

• Issue where streamed responses were not encoded correctly
• Issue where body could throw exception during setting
  • Now catches and sets status code to 500
• Issue where on connect was not being called for WebSocket

Chores #

• Upgrade dependencies

Features #

• Use .then syntax instead of await to handle request operation
  • This allows for faster request handling

Enhancements #

• ByteStreamBodyData now extends StreamBodyData
• Improve server sent event response handling
  • close stream when client disconnects
  • Use new CleanUp class to handle cleanup

Features #

• Add CleanUp class to DataHandler on initialization

Enhancements #

• Handling responses and root errors

Fixes #

• Poor type handling for header values that could cause a response to fail

Features #

• Manage cookies with Headers.cookies and Headers.setCookies

Features | 01.20.25 #

• Manage cookies with Headers.cookies and Headers.setCookies

Features #

• Combine meta types for better polymorphism support
• Add ReadOnlyMeta to MiddlewareContext

Enhancements #

• Rename ReadOnlyDataHandler to ReadOnlyData
• Rename WriteOnlyDataHandler to WriteOnlyData

Fixes #

• Issue where routes would not appear in list of routes after server restart

Features #

• Create ExpectedHeaders as non-optional headers to be passed into the request
• Add ExpectedHeaders to access control headers

Enhancements #

• Re-order the pre-request checks to
  • CORs Origins Validation
  • CORs Headers Validation
  • (CORs) Expected Headers Validation
  • Options Request Handling
  • Redirect Handling
• Return actual response in the OPTIONS request instead of a canned response
• Handle internal root errors with the response handler instead of deprecated send method

Fix #

• Add routes param to SseRoute constructor

Features #

• Support advanced ResponseHandler per route
  • If a response needs to be handled differently for a specific route, a ResponseHandler can be provided to the route to send the response to the client
• Create default response handler for Router
• Create SseRoute for Server-Sent Events
• Create SseResponseHandler for Server-Sent Events

Enhancements #

• Improve how streams are prepared for sending to the client

Chores #

• Upgrade dependencies

• Initial Release