Skip to content

Avoid having PHP class in the message after serialization #292

@vjik

Description

@vjik

Can we avoid having PHP class in the message?

  1. It makes refactoring impossible.
  2. It doesn't make sense for non-PHP or other app consumers.
  3. If there are multiple envelopes... which class should be there?

Originally posted by @samdark in #291 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions