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

LCFS - Allocation agreement view of CI of fuel is showing more than 2 decimal places #1057

Open
Grulin opened this issue Oct 15, 2024 · 0 comments
Labels
bug Something isn't working Compliance Reporting Medium Medium priority

Comments

@Grulin
Copy link
Collaborator

Grulin commented Oct 15, 2024

Describe the Bug
In the Allocation Agreement view table of the compliance report, the CI (Carbon Intensity) number is currently displaying with too many decimal places. It should be limited to only two decimal places for clarity and consistency. The current behavior is displaying many fractional digits, which is not necessary and can be confusing for users.

Expected Behaviour
The CI (Carbon Intensity) number in the Allocation Agreement view table should be limited to only two decimal places (e.g., 45.67).

Actual Behaviour
The CI number is currently displayed with excessive decimal places, making the values appear cluttered and hard to interpret and is inconsistent with our use of 2 decimal places across the application.

Implications

  • Displaying too many decimal places can create confusion and reduce the clarity of the data in the Allocation Agreement view.
  • Users may struggle to accurately interpret the CI number, impacting their ability to review compliance reports effectively.

Steps To Reproduce
Steps to reproduce the behaviour:
User/Role: BCeID

  1. Navigate to the Allocation Agreement view table in the compliance report.
  2. Observe the CI (Carbon Intensity) number displayed with many decimal places.
  3. Note that the CI value should be limited to only two decimal places.
@Grulin Grulin added bug Something isn't working Compliance Reporting Medium Medium priority labels Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Compliance Reporting Medium Medium priority
Projects
None yet
Development

No branches or pull requests

1 participant