Skip to content

Conversation

@ayeshalshukri1-nhs
Copy link
Contributor

@ayeshalshukri1-nhs ayeshalshukri1-nhs commented Apr 22, 2025

Description

AS A developer
I WANT to add a full list of operators from DPS to the rule engine
SO THAT they are available for use in eligibility checks

https://nhsd-jira.digital.nhs.uk/browse/ELI-152

Context

The task here is to compile/transfer a full list of available operators from DPS and implement them for the rule engine.

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.

Copy link
Contributor

Choose a reason for hiding this comment

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

Looks good for now.

Copy link
Collaborator

@eddalmond1 eddalmond1 left a comment

Choose a reason for hiding this comment

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

Good, I've only spotted one potential edge case but mostly looks like what we'd want.

Copy link
Contributor

Choose a reason for hiding this comment

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

Please fix linting errors!

Copy link
Collaborator

@eddalmond1 eddalmond1 left a comment

Choose a reason for hiding this comment

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

Looks good, approved, with the assumption Simon's concerns will be addressed in a subsequent ticket

@ayeshalshukri1-nhs ayeshalshukri1-nhs force-pushed the feature/eli-152-operators-impl branch from be60a1c to e2f845e Compare April 24, 2025 08:15
@ayeshalshukri1-nhs ayeshalshukri1-nhs merged commit c8be207 into main Apr 24, 2025
23 checks passed
@Karthikeyannhs
Copy link
Contributor

Karthikeyannhs commented Apr 24, 2025

.

Copy link
Contributor

Choose a reason for hiding this comment

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

Just thinking, will it be better to group the testscases for a same operator together using test classes for better structuring?

Copy link
Contributor

Choose a reason for hiding this comment

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

@eddalmond1 eddalmond1 deleted the feature/eli-152-operators-impl branch May 21, 2025 13:47
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.

4 participants