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

Bug: Parking Provided / Baseline field displays non-whole numbers #2052

Open
5 tasks
thetanmancan opened this issue Jan 19, 2025 · 0 comments
Open
5 tasks
Labels
bug Release Note: Shows as Error Correction level: medium p-feature: Target Points Page p3 Users enter number of parking spaces /calculation/3 priority: MUST HAVE role: back-end Node/Express Development Task size: 2pt Can be done in 7-12 hours Waiting on Stakeholder
Milestone

Comments

@thetanmancan
Copy link
Member

thetanmancan commented Jan 19, 2025

Overview

We need to make the input field for parking provided only accept whole numbers with a max number allowed.

Details

On Create Project Page 3, the Parking Provided field does not have a character limit. As a result, the user can enter an unrealistically large number. If the user a value greater than or equal to 100,000,000,000,000,008,193 in the field, it causes the number in the Parking Provided / Baseline field to display an exponent instead of a whole number.

Steps to Reproduce

  1. Log into the TDM Dev site.
  2. Navigate to Create Project Page 1.
  3. Enter any valid data in all the required fields.
  4. Click the ">" button.
  5. In the Condominium Units field, enter "16".
  6. In the "Non-Condominium Units with less than 3 habitable rooms" field, enter "1".
  7. In the "Non-Condominium Units with 3 habitable rooms" field, enter "9".
  8. Click the ">" button.
  9. In the Parking Provided field, enter a number greater than or equal to 100,000,000,000,000,008,193 without entering any commas.

Expected Result

A whole number should be displayed. Ideally, an unrealistically large number wouldn't be allowed to be entered in the Parking Provided field, preventing this defect from occurring in the first place.

Actual Result

An exponent appears in the Parking Provided / Baseline field.

Parking Provided / Baseline exponent

Device Configuration

  • Device: Desktop
  • OS version: Windows 11
  • Browser: Firefox
  • Browser version: 134.0.1

Action Items

  • Fix bug by restricting values the front end and back end will accept to whole numbers
  • Ask stakeholder what the max number is.
  • Review with product, design, and development. Update if needed based on feedback.
  • Once finalized, add a slide to the staging deck.
  • Get Stakeholder sign-off via the stakeholder meeting slide deck.
@thetanmancan thetanmancan added bug Release Note: Shows as Error Correction level: missing milestone: missing p-feature: Target Points Page p3 Users enter number of parking spaces /calculation/3 priority: MUST HAVE ready for dev lead role: front-end Front End Developer size: missing labels Jan 19, 2025
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: TDM: project board Jan 19, 2025
@ExperimentsInHonesty ExperimentsInHonesty added this to the 10 - Launch milestone Jan 22, 2025
@ExperimentsInHonesty ExperimentsInHonesty added time sensitive ready for prioritization Issues that are ready to be prioritized by product role: back-end Node/Express Development Task and removed time sensitive ready for dev lead role: front-end Front End Developer labels Jan 22, 2025
@entrotech entrotech moved this from New Issue Approval to Prioritized Backlog in P: TDM: project board Jan 22, 2025
@entrotech entrotech removed the ready for prioritization Issues that are ready to be prioritized by product label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Release Note: Shows as Error Correction level: medium p-feature: Target Points Page p3 Users enter number of parking spaces /calculation/3 priority: MUST HAVE role: back-end Node/Express Development Task size: 2pt Can be done in 7-12 hours Waiting on Stakeholder
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

3 participants