Skip to content

Investigate better ways to organize domain messages in RD domain logic

MR: Pending

Description

Created as a follow-up to this discussion.

Investigate better ways to organize domain messages in RD domain logic. Currently, the messages are grouped first by Errors / Domain messages and then:

  • For Error group: By API
  • For Domain Events group: By model/domain entity

Alternative groupings that can be considered:

  • By API only: this would be make it very easy to reason about the set of outcomes for an API by looking at a co-located group of messages vs having to hop between two different sections (Errors and Domain Events)

TODO: Fill out (required) As a [user or stakeholder], I want [goal or objective] so that [reason or benefit].

Acceptance Criteria

TODO: Fill out (required)

  • [Describe what must be achieved to complete this issue.]
  • [Describe another requirement needed to complete this issue.]
  • [Add additional acceptance criteria as needed.]

Technical Requirements

TODO: Fill out or delete [If applicable, please list out any technical requirements for this feature/enhancement.]

Design Requirements

TODO: Fill out or delete [If applicable, please provide a link to the design specifications for this feature/enhancement.]

Impact Assessment

TODO: Fill out or delete [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.]

User Story

TODO: Fill out or delete [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.]