Skip to content

Rethink DecodedMessage naming #485

@pklaschka

Description

@pklaschka

https://github.com/wuespace/telestion-core/blob/35de85b43f58cb223d77f6ac444817b1dbdea49b/modules/telestion-api/src/main/java/de/wuespace/telestion/api/verticle/trait/DecodedMessage.java

Currently, the DecodedMessage serves as a wrapper for both the Vert.x and our own JsonMessage (representing the message's body) types.

However, DecodedMessage could, by itself, also represent a decoded / I..e, typed, message content, meaning these names collide.

We should probably rethink this naming before v1.0.

Metadata

Metadata

Assignees

No one assigned

    Labels

    💣 breakingIssue or PR that includes breaking changes🍒 on topA feature which doesn't impact the code in a meaningful way but the developer likes it more🚧 bugSomething isn't working📄 javaPull requests that update Java code🔧 telestion-apiEverything related to the telestion-api module

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions