Skip to content

CCM-17993: Update MESHInboxMessageInvalid event#367

Open
ScottFullerton-NHSE wants to merge 3 commits into
mainfrom
feature/CCM-17993-update-mesh-message-invalid-event
Open

CCM-17993: Update MESHInboxMessageInvalid event#367
ScottFullerton-NHSE wants to merge 3 commits into
mainfrom
feature/CCM-17993-update-mesh-message-invalid-event

Conversation

@ScottFullerton-NHSE
Copy link
Copy Markdown
Contributor

@ScottFullerton-NHSE ScottFullerton-NHSE commented May 21, 2026

Description

Updates the MESHInboxMessageInvalid event to use reasonCode.

Context

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@ScottFullerton-NHSE ScottFullerton-NHSE requested a review from a team as a code owner May 21, 2026 09:21
$ref: ../defs/requests.schema.yaml#/properties/senderId
failureCode:
reasonCode:
$ref: ../defs/requests.schema.yaml#/properties/failureCode
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if it would be worth adding a reasonCode property to requests.schema.yaml. I don't think we can get rid of the failureCode type in requests.schema.yaml just yet as it might be used elsewhere.
Also there is a reasonCode in print.schema.yaml but we probably shouldn't use that either.

Copy link
Copy Markdown
Contributor

@simonlabarere simonlabarere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure why the ticket's scope wasn't to get rid of failureCode completely.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants