\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.6299174,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Describe the bug**\nIn the Edit Facility Details form, Facility Name and Address accepts input that contains only whitespace.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Setting > General'\n2. Click on 'Edit Facility Details'\n3. Input Whitespace in Facility Name and Address\n4. Click on Submit\n5. See error\n\n**Expected behavior**\nWhitespaces shall not be accepted.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/3d3617a1-b970-49c2-a31e-99d562f09678\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",[],13832,"Whitespace passes validation in Edit facility details form","2025-09-24T10:36:40Z","https://github.com/ohcnetwork/care_fe/issues/13832",0.6981502,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**Describe the bug**\n\nCreate a new healthcare service with no location and the custom icon, and try to edit the healthcare services in the facility, the validation error will be thrown for empty fields\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to a facility and create a healthcare services with location and icons as empty\n2. edit the newly created healthcare services other than location or icon field\n3. see the error message\n\n**Expected behavior**\n\nOnly throw validation error on submission for mandatory field or whereever necessary\n\n**Screenshots**\n\n\u003Cimg width=\"1165\" height=\"825\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cf5dd63b-e05f-4ec3-8d3b-88e110003390\" />\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",[],13989,"Validation is malfunctioning in the healthcare service edit page","2025-10-07T13:03:03Z","https://github.com/ohcnetwork/care_fe/issues/13989",0.7049136,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**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.7125536,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3207,"title":3208,"updated_at":3209,"url":3210,"score":3211},"**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,"closed","Inconsistent and Technical Validation Errors in “Create Schedule Template” Form","2025-08-11T17:34:26Z","https://github.com/ohcnetwork/care_fe/issues/13304",0.5377777,{"description":3213,"labels":3214,"number":3215,"owner":3172,"repository":3173,"state":3207,"title":3216,"updated_at":3217,"url":3218,"score":3219},"**Description:** Edit Schedule Template Form is accepting white space.\n\nhttps://github.com/user-attachments/assets/78db4434-cdf5-4913-9709-732011f287ca\n\n**Steps to Reproduce:**\n- Navigate to Edit Schedule Template Form.\n- Enter a blank space (\" \") in the Template name Field.\n- Submit the form.\n- Observe that the form accepts the input instead of showing validation error.\n\n---\n\n🚨 DO NOT EDIT BELOW THIS LINE 🚨\nInstructions for Requesting Assignment:\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\nDescribe 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\nExpected Timeline:\n\nEnd date: [Expected submission date of a completed Pull Request]\nAdditional 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\n\n\n",[],13775,"Edit Schedule Template accept blank inputs (\" \")","2025-09-22T08:40:37Z","https://github.com/ohcnetwork/care_fe/issues/13775",0.6237687,{"description":3221,"labels":3222,"number":3223,"owner":3172,"repository":3173,"state":3207,"title":3224,"updated_at":3225,"url":3226,"score":3227},"**Describe the bug**\nIn the **Patient Identifier Config** form and **Tag Config** Form, required fields like `Display`, `Description`, `System` and `Slug` accept only whitespace as valid input. This results in entries that appear blank but still pass validation.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Log in as Super admin\n2. Go to Patient Identifier Config Form or Tag Config Form\n3. Add whitespaces to required field\n4. See error\n\n**Expected behavior**\nWhitespace-only input should be treated as empty. These fields should trigger a **\"Required\"** validation error if the input contains only spaces.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/6df1a10f-c285-44a0-b62a-2a3d23340b8f\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",[],13312,"Whitespace Bypasses Validation in Required Fields in Config Forms","2025-08-22T11:20:01Z","https://github.com/ohcnetwork/care_fe/issues/13312",0.6444405,{"description":3229,"labels":3230,"number":3231,"owner":3172,"repository":3173,"state":3207,"title":3232,"updated_at":3233,"url":3234,"score":3235},"**Describe the bug**\nIn the **Patient Create Form**, the following required fields:\n- Name\n- Current Address \n- Permanent Address\n\nare accepting whitespace-only input (e.g. `\" \"`). Despite being marked as required, the form still allows submission and creates the patient record, saving empty looking values for those fields.\n\nThis breaks the required field validation logic.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Patient Section\n2. Click on Add New patient\n3. Fill the form \n4. See error\n\n**Expected behavior**\nIf a user enters only whitespace in any required field, it should be treated the same as leaving it empty:\n- A validation error should appear (e.g. “This field is required”)\n- The form should not be submitted until valid text is entered\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/eb0cbc78-093f-460a-9b46-a393e4533e7e\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",[],12948,"Whitespace Bypasses Required Validation in Patient Form Fields","2025-07-21T08:05:07Z","https://github.com/ohcnetwork/care_fe/issues/12948",0.6459479,{"description":3237,"labels":3238,"number":3239,"owner":3172,"repository":3173,"state":3207,"title":3240,"updated_at":3241,"url":3242,"score":3243},"**Describe the bug**\nIn the Doctor Schedule Template creation form, the optional `Remarks` field accepts whitespace-only input (e.g. spaces). This gets saved as a valid remark even though no actual content was provided. that may violate UX expectations and unnecessary DB storage\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Log in as a doctor\n2. In the overview page click on My Schedules and then create one Template.\n3. while filling the Remarks field, add only whitespaces\n4. See error\n\n**Expected behavior**\nIf the user enters only whitespace in the `Remarks` field, it should be treated as empty (`null` or `\"\"`) and not be saved or submitted as a valid remark.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/0ae1be48-effc-4065-b393-5b4663f2982e\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",[],12888,"Whitespace-only input in optional \"Remarks\" field is treated as valid text in Create Schedule Template.","2025-07-18T07:01:47Z","https://github.com/ohcnetwork/care_fe/issues/12888",0.655042,{"description":3245,"labels":3246,"number":3253,"owner":3172,"repository":3173,"state":3207,"title":3254,"updated_at":3255,"url":3256,"score":3257},"**Describe the bug**\nwhen the user submits the form with empty fields, the validation messages appear and remain even after the sheet is closed. \nRe-opening the sheet shows the errors.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Users → Availability\n2. Click Create Template (the same happens with Create Exception).\n3. Submit the form without filling any fields.\n4. Close the sheet and open it again.\n5. The previous validation messages are still visible.\n\nhttps://github.com/user-attachments/assets/16089f64-6743-4003-b62d-21dd8042ad4c\n\n\n**Expected behavior**\nAll validation messages should disappear when the sheet is closed.\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",[3247,3250],{"name":3248,"color":3249},"question","d876e3",{"name":3251,"color":3252},"needs-triage","ededed",12802,"Submission Errors Persist After Closing and Re-Opening Form Sheet","2025-07-07T13:09:47Z","https://github.com/ohcnetwork/care_fe/issues/12802",0.68535215,["Reactive",3259],{},["Set"],["ShallowReactive",3262],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fv_WmGnPanmpKGEeVZOfE4CoOnA-VaTCTcg5CrSSzFZU":-1},"/ohcnetwork/care_fe/13694"]