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

Fix std charge transaction presenter for S130 #823

Merged
merged 4 commits into from
Mar 18, 2024

Conversation

Cruikshanks
Copy link
Member

@Cruikshanks Cruikshanks commented Mar 15, 2024

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

Our users reported that for licences where the Canal and Rivers Trust agreement (S130) has been applied, it isn't displayed against the transaction in the new bill view.

We assumed this was just another thing we missed when building the new views. So, we were surprised when we found there is code to handle displaying the Canal and rivers trust agreement.

After doing some digging we found out why 🙄🤦

water-4409_cause

We'd already clocked that for some reason the previous team had made this a text field rather than a boolean, even though we are using it to store true or false. We hadn't clocked was that when the legacy code sets the field it includes a space at the end. Computers being computers means 'true' !== 'true '. 😡

This change updates the code to handle this.

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

Our users reported that for licences where the Canal and Rivers Trust agreement (S130) has been applied it isn't displayed against the transaction in the new bill view.

We assumed this was just another thing we missed when building the new views. So, we were surprised when we found there is code to handle displaying the Canal and rivers trust agreement.

After doing some digging we found out why :rolling_eyes: 🤦‍♂️

We'd already clocked that for some reason the previous team had made this a text field rather than a boolean, even though we are using it to store true or false. We hadn't clocked was that when the legacy code sets the field it is including a space at the end. Computers being computers means 'true' !== 'true '.

This change updates the code to handle this.
@Cruikshanks Cruikshanks added the bug Something isn't working label Mar 15, 2024
@Cruikshanks Cruikshanks self-assigned this Mar 15, 2024
@Cruikshanks Cruikshanks marked this pull request as ready for review March 15, 2024 16:57
Copy link
Contributor

@Jozzey Jozzey left a comment

Choose a reason for hiding this comment

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

Just a console.log to remove

@Cruikshanks Cruikshanks requested a review from Jozzey March 18, 2024 11:27
Copy link
Contributor

@Jozzey Jozzey left a comment

Choose a reason for hiding this comment

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

@Cruikshanks Cruikshanks merged commit 261b6db into main Mar 18, 2024
6 checks passed
@Cruikshanks Cruikshanks deleted the fix-canel-and-river-trust-in-bill-view branch March 18, 2024 11:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants