Skip to content
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

Refactor determining server error type when deserializing an @httpPayload #3752

Merged
merged 3 commits into from
Jul 10, 2024

Commits on Jul 9, 2024

  1. Refactor determining server error type when deserializing an `@httpPa…

    …yload`
    
    Determining the error type when deserializing an `@httpPayload` is a
    protocol-specific concern, and as such should not live in
    `ServerHttpBoundProtocolGenerator`, which should remain
    protocol-agnostic. This commits makes that determination part of the
    `ServerProtocol` interface.
    
    As a drive-by improvement, the companion object in
    `ServerHttpBoundProtocolGenerator` has also been removed, since its
    members have been unused for a long time.
    david-perez committed Jul 9, 2024
    Configuration menu
    Copy the full SHA
    145677d View commit details
    Browse the repository at this point in the history
  2. fix

    david-perez committed Jul 9, 2024
    Configuration menu
    Copy the full SHA
    f1e2ea3 View commit details
    Browse the repository at this point in the history

Commits on Jul 10, 2024

  1. Merge remote-tracking branch 'upstream/main' into davidpz/refactor-de…

    …serialize-payload-error-type
    david-perez committed Jul 10, 2024
    Configuration menu
    Copy the full SHA
    cbeb9e8 View commit details
    Browse the repository at this point in the history