\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],13305,"ohcnetwork","care_fe","open","Validation Errors Not Displayed as Expected for Schedule Edit Form ","2025-08-10T18:45:31Z","https://github.com/ohcnetwork/care_fe/issues/13305",0.7355341,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Describe the bug**\nThere are inconsistent and incorrect validation behaviors in the **Create Schedule Template form**:\n1. Whitespace bypasses required fields\n- Fields like Template Name and Session Title accept whitespace as valid input.\n- Example: entering `\" \"` clears the validation error `\"This field is required\"`.\n\n2. Numeric fields show technical error messages\n- Fields like Slot Duration and Patients per Slot display `\"Expected number, received null\"` when left empty.\n- This is confusing for users and not consistent with other required fields that show `\"This field is required\"`.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Open Create Schedule Template form.\n- Leave Template Name and Session Title empty → `\"This field is required\"` error appears.\n- Enter only spaces in these fields → error disappears incorrectly.\n- Leave Slot Duration or Patients per Slot empty → error shows `\"Expected number, received null\"`.\n\n**Expected behavior**\n- Whitespace-only input should be treated as empty and trigger `\"This field is required\"`.\n- Numeric fields should also display a user-friendly message like `\"This field is required\"` instead of technical error text.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/32c48372-f924-484d-8555-d868f78b6eea\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],13694,"Validation Issues in Create Schedule Template Form","2025-09-12T09:37:28Z","https://github.com/ohcnetwork/care_fe/issues/13694",0.73990035,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**Describe the bug**\nWhen toggling the Auto-fill slot duration switch in the schedule template form, the Number of slots input throws a React warning:\n\"Input contains an input of type number with both value and defaultValue props.\nInput elements must be either controlled or uncontrolled (specify either the value prop, or the defaultValue prop, but not both).\"\n\nThis happens because the Input component is being passed both value (from react-hook-form) and defaultValue simultaneously.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to overview → Users → Create Schedule Template.\n2. Scroll to the Auto-fill slot duration toggle and enable it.\n3. The Number of slots input becomes visible.\n4. Observe the console warning in DevTools.\n\n**Expected behavior**\nThe input field should work without throwing controlled/uncontrolled warnings. It should only use value (via react-hook-form) or defaultValue (but not both).\n\n**Screenshots**\n\n\u003Cimg width=\"1917\" height=\"994\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/961f8b18-057f-4586-b67a-6769967b5ef2\" />\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nThe issue is caused in FormField → Input usage:\n\n\u003CInput\n type=\"number\"\n min={1}\n defaultValue={1} // ❌ conflict\n {...field} // includes value + onChange\n/>\n\nThis passes both value and defaultValue, leading to the React error.\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],13574,"Bug: Input field throws controlled/uncontrolled warning when using auto-fill slot duration toggle","2025-08-31T10:24:24Z","https://github.com/ohcnetwork/care_fe/issues/13574",0.7409727,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3199,"title":3200,"updated_at":3201,"url":3202,"score":3203},"**Describe the bug**\nWhen creating a schedule exception , the date picker does not disable past dates, \nbut the schedule template creation sheet correctly disables past dates in the date picker.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Users' → \"Availability\".\n2. Open the \"Add Exception\" sheet.\n3. Observe that the date picker allows selecting past dates .\n4. Compare with the schedule template creation sheet, where past dates are disabled in the date picker.\n\nhttps://github.com/user-attachments/assets/96281f03-6c95-46fd-ba36-d2695041bb65\n\n**Expected behavior**\nA clear and concise description of what you expected to happen.\n\n**Screenshots**\nPast dates should be disabled in the date picker for schedule exceptions, matching the behavior of the schedule template creation sheet.\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],13091,"closed","Past Dates Not Disabled in Schedule Exception Date Picker","2025-07-31T11:37:28Z","https://github.com/ohcnetwork/care_fe/issues/13091",0.7121446,{"description":3205,"labels":3206,"number":3207,"owner":3172,"repository":3173,"state":3199,"title":3208,"updated_at":3209,"url":3210,"score":3211},"**Describe the bug**\nUsers can currently create schedule exceptions that overlap in date and time with existing ones.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'My Schedules'\n2. Click on 'Add Exception'\n3. Add a schedule exception for a specific date/time.\n4. Add another exception with overlapping date and time.\n5. See error\n\n**Expected behavior**\nPrevent submission if the new exception overlaps with any existing one.\n\n**Screenshots**\n\n\u003Cimg width=\"1919\" height=\"977\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8a97bce5-5e6a-40a9-81b6-5eca01f2b369\" />\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],13138,"Prevent Duplicate Schedule Exceptions","2025-08-02T06:19:51Z","https://github.com/ohcnetwork/care_fe/issues/13138",0.7211854,{"description":3213,"labels":3214,"number":3215,"owner":3172,"repository":3173,"state":3199,"title":3216,"updated_at":3217,"url":3218,"score":3219},"**Describe the bug**\nWhen adding a user exception, the validation error message does not clear immediately after the user checks the checkbox , but the form is submitted.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Users → Click \"Add Exception\"\n2. Observe that the error messages persists after checking the checkbox.\n\nhttps://github.com/user-attachments/assets/90cc5bcc-3fe6-4ac1-b313-59540bccb70b\n\n\n**Expected behavior**\nThe error message should disappear as the user checks the checkbox.\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],12803,"Validation Message Fails to Clear on Checkbox Toggle","2025-07-16T12:13:25Z","https://github.com/ohcnetwork/care_fe/issues/12803",0.7244527,{"description":3221,"labels":3222,"number":3229,"owner":3172,"repository":3173,"state":3199,"title":3230,"updated_at":3231,"url":3232,"score":3233},"**Describe the bug**\n\nWhen we submit the form, and there is a error in the schedule create form / edit form, it is not auto scrolling to the error message, so users need to manually check for error\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to profile and create a schedule with past date\n2. submit the form\n3. See error\n\n**Expected behavior**\n\nAuto-scroll to the error message in the schedule create / edit form\n\n**Screenshots**\n\n\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[3223,3226],{"name":3224,"color":3225},"question","d876e3",{"name":3227,"color":3228},"needs-triage","ededed",12149,"Add auto-scroll to error fields in schedule creation / edit form","2025-07-22T07:37:10Z","https://github.com/ohcnetwork/care_fe/issues/12149",0.7283074,{"description":3235,"labels":3236,"number":3239,"owner":3172,"repository":3173,"state":3199,"title":3240,"updated_at":3241,"url":3242,"score":3243},"**Describe the bug**\nExceptions starting and ending on the same day currently show `from \u003Cdate> to \u003Csame date>`, repeating the same date.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'My Schedules'\n2. Click on 'Exceptions' -> 'Add Exception'\n3. Create an exception where start day and end day are the same\n4. See error\n\n**Expected behavior**\nIf the start and end dates are the same, display only one date. Example:\n`12 AM – 11:59 PM on Wed, 06 Aug 2025` instead of repeating the date.\n\n**Screenshots**\n\n\u003Cimg width=\"892\" height=\"155\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e598a6a2-9680-4060-bc3c-e552ace2c9c7\" />\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[3237,3238],{"name":3224,"color":3225},{"name":3227,"color":3228},13359,"Simplify same-day exception date display","2025-08-19T06:35:43Z","https://github.com/ohcnetwork/care_fe/issues/13359",0.7355254,{"description":3245,"labels":3246,"number":3247,"owner":3172,"repository":3173,"state":3199,"title":3248,"updated_at":3249,"url":3250,"score":3251},"**Describe the bug**\nIn the **Create Schedule Template form**, when the form is submitted with empty values, most fields correctly show user-friendly validation errors such as `\"This field is required\"`.\nHowever, the fields `Slot Duration` and `Patients per Slot` display raw validation errors:\n- `\"Expected number, received null\"` when left empty.\n- `\"Expected number, received nan\"` when input is typed and then cleared.\n\nThis results in a confusing and inconsistent user experience, especially for non-technical users\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Create Schedule Template page.\n2. Leave all fields empty and click **Save**.\n3. Observe the validation messages for all required fields.\n4. See error\n\n**Expected behavior**\nAll fields should show consistent and user-friendly validation messages:\n- If empty: `This field is required`\n- If invalid: `Please enter a valid number`\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/44622cee-2151-480f-aba6-2c2216c2b81e\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],13304,"Inconsistent and Technical Validation Errors in “Create Schedule Template” Form","2025-08-11T17:34:26Z","https://github.com/ohcnetwork/care_fe/issues/13304",0.7391692,{"description":3253,"labels":3254,"number":3258,"owner":3172,"repository":3173,"state":3199,"title":3259,"updated_at":3260,"url":3261,"score":3262},"**Describe the bug**\nIn the Patient details form when a user accidentally clicks on patient deceased checkbox and then toggles it after a validation error the form is not getting submitted. This creates confusion among users\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Patient Detail form\n2. See error\n\nhttps://github.com/user-attachments/assets/2d624192-0fa9-4a9d-b268-763df55dd02c\n\n**Expected behavior**\nWhen we click on the deceased checkbox accidentally and submit and then toggle the checkbox and then submit the form must get submitted and the validation error must be cleared on toggling the checkbox\n\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[3255],{"name":3256,"color":3257},"needs review","CCF900",13162,"Patient deceased date time validation error message is not getting cleared even after the deceased checkbox is not marked","2025-08-19T07:00:20Z","https://github.com/ohcnetwork/care_fe/issues/13162",0.7454985,["Reactive",3264],{},["Set"],["ShallowReactive",3267],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRwrkIZPFKjd1zS3CBQgZAOAW_kca6zktajuO56lAHqg":-1},"/ohcnetwork/care_fe/13538"]