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

Add review badge, rename existing and call it tag! #885

Merged
merged 11 commits into from
Apr 4, 2024

Conversation

Cruikshanks
Copy link
Member

https://eaflood.atlassian.net/browse/WATER-4370

A long time back we created a macro for displaying 'badges' for bill runs. These are GOV.UK tag components and indicate the status of a bill run.

We have to display them in so many places it is the only thing to justify having a macro so far.

In the work we are doing building the review two-part tariff matches and allocations views we again need badges for statuses.

Great! We have a 'badge' macro. Only there are differences. ready for bill runs should be displayed as blue. In the review screens it needs to be green. Also, the badges need to be different sizes for the two contexts.

We had it in mind to expand the existing functionality but that was what made it clear we needed two different badges for the 2 contexts.

This means the existing badge.njk macro should also be given a more explicit name.

Then the final change; stop calling these blooming things badges. They're tags!

https://eaflood.atlassian.net/browse/WATER-4370

A long time back we created a macro for displaying 'badges' for bill runs. These are [GOV.UK tag components](https://design-system.service.gov.uk/components/tag/) and indicate the status of a bill run.

We have to display them in so many places it is the only thing to justify having a macro so far.

In the work we are doing building the review two-part tariff matches and allocations views we again need badges for statuses.

Great! We have a 'badge' macro. Only there are differences. `ready` for bill runs should be displayed as blue. In the review screens it needs to be green. Also, the badges need to be different sizes for the two contexts.

We had it in mind to [expand the existing functionality](#882) but that was what made it clear we really need two different badges for the 2 contexts.

Which means the existing `badge.njk` macro should also be given a more explicit name.

Then the final change; stop calling these blooming things badges. They're tags!
We've excluded where the review licence badge is using it but that's because we intend to use our new review-status-tag. All the rest have been updated though.
@Cruikshanks Cruikshanks added the housekeeping Refactoring, tidying up or other work which supports the project label Apr 3, 2024
@Cruikshanks Cruikshanks self-assigned this Apr 3, 2024
@Cruikshanks Cruikshanks marked this pull request as ready for review April 3, 2024 23:24
@Cruikshanks Cruikshanks requested a review from Beckyrose200 April 3, 2024 23:24
Copy link
Contributor

@Beckyrose200 Beckyrose200 left a comment

Choose a reason for hiding this comment

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

This is much nicer and looks cleaner than what I had going on :)

@Cruikshanks Cruikshanks merged commit 905675f into main Apr 4, 2024
6 checks passed
@Cruikshanks Cruikshanks deleted the add-review-badge-macro branch April 4, 2024 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
housekeeping Refactoring, tidying up or other work which supports the project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants