Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POLIO-1762 POLIO-1764 POLIO-1765: Campaign combination cVDPV1 & cVDPV2 w/ 2 vaccines nOPV2 & bOPV #1876

Merged
merged 24 commits into from
Dec 19, 2024

Conversation

beygorghor
Copy link
Collaborator

We will have to create a new Virus Type: cVDPV1 & cVDPV2 with the Vaccine Type: nOPV2 & bOPV associated

Related JIRA tickets POLIO-1762

Self proofreading checklist

  • Did I use eslint and black formatters
  • Is my code clear enough and well documented
  • Are my typescript files well typed
  • New translations have been added or updated if new strings have been introduced in the frontend
  • My migrations file are included
  • Are there enough tests
  • Documentation has been included (for new feature)

Changes

  • added new constants
  • implement new hashed colors as shape color

How to test

  • Open scope for a campaign, you should have nOPV2 & bOPV option in the vaccines.
  • Create a campaign, try to select cVDPV1 & cVDPV2 as virus.

If a specific config is required explain it here: dataset, account, profile, etc.

Print screen / video

Screenshot 2024-12-17 at 15 26 13

Follow the Conventional Commits specification

The merge message of a pull request must follow the Conventional Commits specification.

This convention helps to automatically generate release notes.

Use lowercase for consistency.

Example:

fix: empty instance pop up

Refs: IA-3665

Note that the Jira reference is preceded by a line break.

Both the line break and the Jira reference are entered in the Add an optional extended description… field.

Copy link
Member

@quang-le quang-le left a comment

Choose a reason for hiding this comment

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

The global feature still needs some spec and this PR will have to be released together with changes in the vaccine module, so I tagged is as DO NOT MERGE in the meantime.

About the feature itself:
Nothing shocking in the code

  • The hashed colors don't appear on the calendar
Screen.Recording.2024-12-18.at.12.08.43.mov
  • They don't appear in the xlsx export of the calendar either:

Screenshot 2024-12-18 at 12 17 18

Copy link
Member

Choose a reason for hiding this comment

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

❤️

Comment on lines +20 to +23
{
label: 'nOPV2 & bOPV',
value: 'nOPV2 & bOPV',
},
Copy link
Member

Choose a reason for hiding this comment

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

This is not correct: supplychain will still handle the vaccines separately. I'll open a separate ticket for that as it will require some backend as well I think

@beygorghor beygorghor changed the title POLIO-1762: Campaign combination cVDPV1 & cVDPV2 w/ 2 vaccines nOPV2 & bOPV POLIO-1762 POLIO-1764 POLIO-1765: Campaign combination cVDPV1 & cVDPV2 w/ 2 vaccines nOPV2 & bOPV Dec 18, 2024
@beygorghor
Copy link
Collaborator Author

Screenshot 2024-12-18 at 16 46 56
@quang-le i have adapted the calendar with the correct colors. Respected tickets have been created.

@beygorghor beygorghor requested a review from quang-le December 19, 2024 10:28
@beygorghor beygorghor merged commit 91c977e into main Dec 19, 2024
4 checks passed
@beygorghor beygorghor deleted the POLIO-1762-nOPV2-bOPV-cVDPV2-cVDPV3 branch December 19, 2024 14:57
@beygorghor beygorghor added the user tested Has already been tested on staging label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user tested Has already been tested on staging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants