Skip to content

Conversation

@Akol125
Copy link
Contributor

@Akol125 Akol125 commented Sep 29, 2025

Summary

  • Routine Change
  • ❗ Breaking Change
  • 🤖 Operational or Infrastructure Change
  • ✨ New Feature
  • ⚠️ Potential issues that might be caused by this change

Add any other relevant notes or explanations here. Remove this line if you have nothing to add.

Reviews Required

  • Dev
  • Test
  • Tech Author
  • Product Owner

Review Checklist

ℹ️ This section is to be filled in by the reviewer.

  • I have reviewed the changes in this PR and they fill all or part of the acceptance criteria of the ticket, and the code is in a mergeable state.
  • If there were infrastructure, operational, or build changes, I have made sure there is sufficient evidence that the changes will work.
  • I have ensured the changelog has been updated by the submitter, if necessary.

@github-actions
Copy link
Contributor

This branch is working on a ticket in the NHS England VED JIRA Project. Here's a handy link to the ticket:

VED-375

Copy link
Contributor

@dlzhry2nhs dlzhry2nhs left a comment

Choose a reason for hiding this comment

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

Couple of changes requested and queries about test cases.

Overall change looks good - in the right direction and the tests are well constructed.

"""
# TODO: is disease type a mandatory field? (I assumed it is)
# i.e. Should we provide a search option for getting Patient's entire imms history?
if not nhs_number_mod11_check(nhs_number):
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we do something about the above TODOs? One to check with business or product. Think point 1 we can just remove - from the validation it is clearly a mandatory field.

From point 2, I think this might be beyond the scope of our API but it might be worth checking. Once we know, let's remove it because we should try to get rid of comments and TODOs like this in the codebase unless it actually needs action.

Copy link
Contributor

Choose a reason for hiding this comment

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

Reason being that legacy comments like this are confusing and introduce uncertainty.

Copy link
Contributor

Choose a reason for hiding this comment

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

Can we do anything with the TODOs now that we have clarified with Martin?

@dlzhry2nhs dlzhry2nhs self-requested a review October 1, 2025 13:34
dlzhry2nhs
dlzhry2nhs previously approved these changes Oct 1, 2025
@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 1, 2025

@Akol125 Akol125 enabled auto-merge (squash) October 1, 2025 17:02
@Akol125 Akol125 disabled auto-merge October 1, 2025 18:11
@Akol125 Akol125 enabled auto-merge (squash) October 1, 2025 19:33
@Akol125 Akol125 dismissed JamesW1-NHS’s stale review October 1, 2025 19:34

comments have been addressed

@Akol125 Akol125 merged commit ebdf18e into master Oct 1, 2025
7 checks passed
@Akol125 Akol125 deleted the VED-375-parameter-errors branch October 1, 2025 19:34
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