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

Contacts flow #60

Merged
merged 5 commits into from
Nov 29, 2024
Merged

Contacts flow #60

merged 5 commits into from
Nov 29, 2024

Conversation

cryptosalomao
Copy link
Collaborator

No description provided.

@cryptosalomao cryptosalomao self-assigned this Nov 16, 2024
Copy link

vercel bot commented Nov 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
e-bill-frontend ✅ Ready (Inspect) Visit Preview Nov 25, 2024 4:12am

Copy link

codecov bot commented Nov 16, 2024

Codecov Report

Attention: Patch coverage is 1.62602% with 121 lines in your changes missing coverage. Please review.

Project coverage is 5.40%. Comparing base (398ea08) to head (c7aff91).

Files with missing lines Patch % Lines
src/pages/contacts/Overview.tsx 0.00% 116 Missing ⚠️
src/main.tsx 0.00% 5 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff            @@
##            main     #60      +/-   ##
========================================
- Coverage   5.55%   5.40%   -0.16%     
========================================
  Files         41      42       +1     
  Lines       3059    3182     +123     
  Branches      19      59      +40     
========================================
+ Hits         170     172       +2     
- Misses      2889    3010     +121     
Flag Coverage Δ
unittests 5.40% <1.62%> (-0.16%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@zupzup zupzup left a comment

Choose a reason for hiding this comment

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

LGTM 👍

<Input id="dateOfBirth" label="Date of birth (MM/DD/YYYY" />
<Select>
<SelectTrigger label="Country of issuing" id="countryOfIssuing">
<SelectValue placeholder="Select an option" />
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should placeholders already be localized with FormattedMessage?

Suggested change
<SelectValue placeholder="Select an option" />
<SelectValue placeholder={<FormattedMessage
id="pages.createContact.select.country"
defaultMessage="Select an option"
description="Placeholder for country selection"
/>} />

This applies to other non-translated fields/placeholders/etc. in this file.

Copy link
Contributor

@mtbitcr mtbitcr Nov 25, 2024

Choose a reason for hiding this comment

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

@mjkeaton just FYI please check #85

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good catch, thank you! I'm gonna replace that. In this case, we must use the imperative API so we don't have to change the typedef for the component.

Ref: https://formatjs.github.io/docs/react-intl/api/#useintl-hook

Copy link
Collaborator

@mjkeaton mjkeaton left a comment

Choose a reason for hiding this comment

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

There is manual work necessary when reviewing the screens. It would be nice if the page routes are registered so that one can browse them without changing the code for the review process. e.g. reaching the empty list screen like for notifications (/notifications-empty) or bills (/bills-empty). What do you think?

Other than that: Looks nice. Approved. 💪

@mtbitcr
Copy link
Contributor

mtbitcr commented Nov 25, 2024

There is manual work necessary when reviewing the screens. It would be nice if the page routes are registered so that one can browse them without changing the code for the review process. e.g. reaching the empty list screen like for notifications (/notifications-empty) or bills (/bills-empty). What do you think?

Other than that: Looks nice. Approved. 💪

agree

@cryptosalomao
Copy link
Collaborator Author

There is manual work necessary when reviewing the screens. It would be nice if the page routes are registered so that one can browse them without changing the code for the review process. e.g. reaching the empty list screen like for notifications (/notifications-empty) or bills (/bills-empty). What do you think?

Other than that: Looks nice. Approved. 💪

We can do that with Storybook. Will add it to the PR. Thanks!

@cryptosalomao cryptosalomao merged commit 8c57be7 into main Nov 29, 2024
3 of 4 checks passed
@cryptosalomao cryptosalomao deleted the flow/contacts branch November 29, 2024 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants