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

Improve the Date and Time component in the CARE #8994

Closed
4 tasks
nihal467 opened this issue Nov 4, 2024 · 13 comments
Closed
4 tasks

Improve the Date and Time component in the CARE #8994

nihal467 opened this issue Nov 4, 2024 · 13 comments

Comments

@nihal467
Copy link
Member

nihal467 commented Nov 4, 2024

Describe the bug

  • Regardless of the user's system time preference, the text field displays time in 24-hour format, while the selection component defaults to a 12-hour format. This inconsistent behavior is not ideal for a component.
  • It is not possible to input "01" in the minutes part of the component; the input text area always shows "1," automatically removing the "0" for single-digit entries.

To Reproduce
Steps to reproduce the behavior:

  1. Go to patient consultation page
  2. Click on edit consultation consultation
  3. Scroll down to admission date
  4. See error

Expected behavior

  • The text area and selection component for date and time should align with the user’s system time preference.
  • Users should be allowed to enter "01" in the minutes part of the component. Similarly, this behavior should be allowed for all other date and hour parts as well

Screenshots

Image
Image

@Keerthilochankumar
Copy link
Contributor

I want to work on this issue. assign it to me.

@SwanandBhuskute
Copy link
Contributor

I would like to work on this @nihal467

@github-project-automation github-project-automation bot moved this to Triage in Care Nov 5, 2024
@rithviknishad rithviknishad moved this from Triage to Up Next in Care Nov 5, 2024
@bodhish
Copy link
Member

bodhish commented Nov 10, 2024

@Keerthilochankumar are you working on this? If yes please do create a draft PR and tag it with the issue.

@Sancharisingh
Copy link

@bodhish I would like to work on this issue. Could you please assign it to me?

@Keerthilochankumar
Copy link
Contributor

@bodhish the work is done i will make pr by the night

@rithviknishad
Copy link
Member

@Keerthilochankumar unassigned due to inactivity. @Sancharisingh do you want to take this up?

@Jeffrin2005
Copy link
Contributor

Jeffrin2005 commented Dec 3, 2024

@Sancharisingh, would you like to work on it? If not, I would be happy to take it on

@github-actions github-actions bot added needs-triage question Further information is requested labels Dec 3, 2024
@Sancharisingh
Copy link

@rithviknishad Yes, I would like to take this up. Please assign it to me.

@saikiranpatil
Copy link

@nihal467 i have created a PR, please review it

@Sancharisingh
Copy link

@AdityaJ2305 I am working on this issue.

@AdityaJ2305
Copy link
Contributor

@saikiranpatil has closed PR so I thought he is not working on it anymore

@Jacobjeevan
Copy link
Contributor

@Sancharisingh Any update on this?

@rajku-dev
Copy link
Contributor

@Sancharisingh Any update on this?

@Jacobjeevan Please consider assigning this issue to me if its not being currently worked on.

@rithviknishad rithviknishad closed this as not planned Won't fix, can't repro, duplicate, stale Dec 31, 2024
@github-project-automation github-project-automation bot moved this from Up Next to Done in Care Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done