Skip to content

Refactor Message for better type safety #166

Description

@github-actions
  • Potentially refactor to individual enums for better case exhaustiveness, covering the cases below...
    • success, error
    • request, response
    • server, client
  • Maybe make a macro that casts a Body::Message based on Body::Type
  • Add a macro for simply defining messages

# TODO: Refactor Message for better type safety
# - Potentially refactor to indivual enums for better case exhaustiveness
# - success, error
# - request, response
# - server, client
# - Maybe make a macro that casts a Body based on `Body::Type`
# - Add a macro for simply defining messages

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions