-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generic request decoder and response encoder #353
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,12 +35,6 @@ | |
|
||
/// Request context values required by Hummingbird itself. | ||
public struct HBCoreRequestContext: Sendable { | ||
/// Request decoder | ||
@usableFromInline | ||
var requestDecoder: HBRequestDecoder | ||
/// Response encoder | ||
@usableFromInline | ||
var responseEncoder: HBResponseEncoder | ||
/// ByteBuffer allocator used by request | ||
@usableFromInline | ||
let allocator: ByteBufferAllocator | ||
|
@@ -54,13 +48,9 @@ | |
|
||
@inlinable | ||
public init( | ||
requestDecoder: HBRequestDecoder = NullDecoder(), | ||
responseEncoder: HBResponseEncoder = NullEncoder(), | ||
allocator: ByteBufferAllocator, | ||
logger: Logger | ||
) { | ||
self.requestDecoder = requestDecoder | ||
self.responseEncoder = responseEncoder | ||
self.allocator = allocator | ||
self.logger = logger | ||
self.endpointPath = .init() | ||
|
@@ -71,21 +61,21 @@ | |
/// Protocol that all request contexts should conform to. Holds data associated with | ||
/// a request. Provides context for request processing | ||
public protocol HBBaseRequestContext: Sendable { | ||
associatedtype Decoder: HBRequestDecoder = NullDecoder | ||
associatedtype Encoder: HBResponseEncoder = NullEncoder | ||
Comment on lines
+64
to
+65
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This will need fixing in HBLambda There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yep, PR on its way |
||
|
||
/// Core context | ||
var coreContext: HBCoreRequestContext { get set } | ||
/// Maximum upload size allowed for routes that don't stream the request payload. This | ||
/// limits how much memory would be used for one request | ||
var maxUploadSize: Int { get } | ||
/// Request decoder | ||
var requestDecoder: Decoder { get } | ||
/// Response encoder | ||
var responseEncoder: Encoder { get } | ||
} | ||
|
||
extension HBBaseRequestContext { | ||
/// Request decoder | ||
@inlinable | ||
public var requestDecoder: HBRequestDecoder { coreContext.requestDecoder } | ||
/// Response encoder | ||
@inlinable | ||
public var responseEncoder: HBResponseEncoder { coreContext.responseEncoder } | ||
/// ByteBuffer allocator used by request | ||
@inlinable | ||
public var allocator: ByteBufferAllocator { coreContext.allocator } | ||
/// Logger to use with Request | ||
|
@@ -109,6 +99,14 @@ | |
public var id: String { self.logger[metadataKey: "hb_id"]!.description } | ||
} | ||
|
||
extension HBBaseRequestContext where Decoder == NullDecoder { | ||
public var requestDecoder: Decoder { NullDecoder() } | ||
} | ||
|
||
extension HBBaseRequestContext where Encoder == NullEncoder { | ||
public var responseEncoder: Encoder { NullEncoder() } | ||
} | ||
|
||
/// Protocol for a request context that can be created from a NIO Channel | ||
public protocol HBRequestContext: HBBaseRequestContext { | ||
/// initialize an `HBRequestContext` | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to make these primary associated types?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure that is necessary. When are you going to need to specify the encoder in a parameter type