Skip to content

Conversation

thomasleese
Copy link
Contributor

If there are duplicate records or not administered records, we want to include this information in a warning callout at the top of the page.

The warning callout component is part of the NHS design system, but not part of GOV.UK's so we don't have a component in govuk-components for it. As this is the first time we're using it, I decided against creating a component for it, but we might want to do add one in the future.

Screenshots

Screenshot 2024-08-23 at 16 54 15

@thomasleese thomasleese requested a review from a team as a code owner August 23, 2024 16:10
Base automatically changed from check-and-confirm to main August 26, 2024 08:57
This allows us to store the count statistics related to immunisation
imports so they can be displayed to the user.
This updates the import process to ensure that we capture the statistics
and store them on the immunisation imports.
@thomasleese thomasleese force-pushed the immunisation-import-stats branch from a1a8045 to 5a6d002 Compare August 26, 2024 08:58
If there are duplicate records or not administered records, we want to
include this information in a warning callout at the top of the page.

The warning callout component is part of the NHS design system, but not
part of GOV.UK's so we don't have a component in govuk-components for
it. As this is the first time we're using it, I decided against creating
a component for it, but we might want to do add one in the future.
@thomasleese thomasleese force-pushed the immunisation-import-stats branch from 5a6d002 to a6b9278 Compare August 26, 2024 09:00
@tvararu tvararu temporarily deployed to mavis-pr-1673 August 26, 2024 09:00 Inactive
Copy link

@thomasleese thomasleese enabled auto-merge (rebase) August 26, 2024 09:01
@thomasleese thomasleese merged commit e6d95ce into main Aug 26, 2024
11 checks passed
@thomasleese thomasleese deleted the immunisation-import-stats branch August 26, 2024 09:03
Copy link
Contributor

@misaka misaka left a comment

Choose a reason for hiding this comment

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

Sorry, this comment got caught in the rebase and turned into a review comment. Not a blocker, but just wondering if we really need to accommodate that code path.

errors.add(column, :blank) if send(column).nil?
end
else
COUNT_COLUMNS.each do |column|
Copy link
Contributor

Choose a reason for hiding this comment

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

When would this path ever be taken? Do we really need to account for it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I was in two minds about whether it was worth doing, I put it in because it is a requirement for the stats to have been calculated if it's processed, but you're right that there's only one code paths which processes these. I figured there was no harm in having it in there, and best case it'll spot perhaps a manual update to the records in the future.

Copy link
Contributor

Choose a reason for hiding this comment

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

Would it make sense to use something that would raise here? That would give us an alert in Sentry which might be a clearer indication of our intention here.

But ¯\_(ツ)_/¯ ... :shipit: first

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