Skip to content

CCM-13378: Handle no supplier available#552

Open
nhsd-david-wass wants to merge 26 commits intomainfrom
feature/CCM-13378-Handle-No-Supplier-Available
Open

CCM-13378: Handle no supplier available#552
nhsd-david-wass wants to merge 26 commits intomainfrom
feature/CCM-13378-Handle-No-Supplier-Available

Conversation

@nhsd-david-wass
Copy link
Copy Markdown
Contributor

Description

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

DT3-Specific Checklist

  • If I have added a new resource (SQS, Lambda, Gateway, DDB table, etc), I have created the appropriate alarms

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.

@nhsd-david-wass nhsd-david-wass requested review from a team as code owners April 29, 2026 13:14
@nhsd-david-wass nhsd-david-wass force-pushed the feature/CCM-13378-Handle-No-Supplier-Available branch 8 times, most recently from 4f77e15 to 7f516e2 Compare May 6, 2026 10:22
stevebux
stevebux previously approved these changes May 6, 2026
const supplier =
!supplierSpec || !supplierSpec.supplierId
!allocationDetails?.supplierSpec ||
!allocationDetails?.supplierSpec.supplierId
Copy link
Copy Markdown
Contributor

@stevebux stevebux May 6, 2026

Choose a reason for hiding this comment

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

I'm just trying to understand when supplierSpec and/or supplierId would be falsy. They're both mandatory fields on their respective parents (and supplierId can't be the empty string), so I think it would only happen when allocationDetails is undefined. If that's correct you may be able to simplify this logic

@nhsd-david-wass nhsd-david-wass force-pushed the feature/CCM-13378-Handle-No-Supplier-Available branch from e997f67 to 4027cc4 Compare May 6, 2026 14:10
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.

3 participants