Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Update input class for proper sizing #1289

Merged
merged 28 commits into from
Jun 16, 2020
Merged

Update input class for proper sizing #1289

merged 28 commits into from
Jun 16, 2020

Conversation

Dmac26
Copy link
Contributor

@Dmac26 Dmac26 commented Apr 10, 2020

Summary

Addresses Issue #1213

This code update completes the 1213 card by updating all related .html, .ts, and .scss files to ensure that all numeric fields referenced in the 1213 card have their width reduced and validation updated to allow numeric ranges to be input with dashes included.

This pull request is ready to merge when...

  • Feature branch starts with the issue number
  • Is connected to its original issue via zenhub 👇
  • All tests are passing and meet coverage, linting, and accessibility requirements. And no security vulnerabilities ⚫️(Circle)
  • This code has been reviewed by someone other than the original author

Copy link
Member

@briandavidson briandavidson left a comment

Choose a reason for hiding this comment

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

Is there any reason we can't use type="number" on the <input> to designate it as for numbers?

@briandavidson briandavidson self-requested a review May 22, 2020 20:06
Copy link
Member

@briandavidson briandavidson left a comment

Choose a reason for hiding this comment

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

@Dmac26 seeing some issues on this one:

image

  • The form section descriptions should be bold i.e "Anticipated number of trips"
  • There is no validation text for the "Anticipated number of trips" field
  • "Anticipated party size" field incorrectly allows text characters

@Dmac26
Copy link
Contributor Author

Dmac26 commented Jun 10, 2020

@briandavidson @mtlaney - I reached out to Aquib to verify what to do with the labels here. I advised me to keep that text unbolded. I fixed everything else though. Please review the corrections when you can.

Copy link
Member

@briandavidson briandavidson left a comment

Choose a reason for hiding this comment

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

Along with the other requested changes, please revert your changes to server/package.json, and omit both server/package-lock.json and frontend/package-lock.json from the PR.

Copy link
Contributor

@mtlaney mtlaney left a comment

Choose a reason for hiding this comment

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

Couple of small tweaks but overall looks good! Nice work Dylan

Copy link
Contributor

@mtlaney mtlaney left a comment

Choose a reason for hiding this comment

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

g2g

@Dmac26 Dmac26 requested review from briandavidson and removed request for briandavidson June 16, 2020 21:45
Copy link
Member

@briandavidson briandavidson left a comment

Choose a reason for hiding this comment

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

There was one remaining "Resolve Conversation" button to click. I was feeling brave so I went ahead and clicked it for ya 😁

I know we had talked about it on slack too but just a reminder, going forward feel free to hit that button and request a re-review and it'll help get these moving along quicker. Nice work! 💥

@Dmac26 Dmac26 merged commit 2271049 into dev Jun 16, 2020
@abdul-fs abdul-fs mentioned this pull request Jul 2, 2020
9 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants