\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",[],13274,"ohcnetwork","care_fe","open","Fix the spacing in the patient notes post submission ( Patient encounter & details page )","2025-08-06T07:02:56Z","https://github.com/ohcnetwork/care_fe/issues/13274",0.6730544,{"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.6786785,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**Describe the bug**\nA clear and concise description of what the bug is.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to '...'\n2. Click on '....'\n3. Scroll down to '....'\n4. See error\n\n**Expected behavior**\nA clear and concise description of what you expected to happen.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/2499c247-eb17-463b-ae65-21c466d9d90c\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",[],13954,"Queue & Service Point Forms Allow Whitespace and Enable Update Button Without Changes","2025-10-06T12:18:39Z","https://github.com/ohcnetwork/care_fe/issues/13954",0.6902039,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"## Describe \nOn referring to video attached below, you would observe there is unnecessary blank space present only for Notes tab on Patient home page which can be filled \n\nhttps://github.com/user-attachments/assets/dfe108f5-3152-4c81-b0e7-19d2b7f45417\n\n## Expected \nEither we can show Actions like we are showing for every other tab or increase the width of messaging block to cover the space \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",[],13224,"Blank space on right side of notes tab in patient home page","2025-08-03T10:41:42Z","https://github.com/ohcnetwork/care_fe/issues/13224",0.70617944,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3174,"title":3207,"updated_at":3208,"url":3209,"score":3210},"**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.7110113,{"description":3212,"labels":3213,"number":3217,"owner":3172,"repository":3173,"state":3218,"title":3219,"updated_at":3220,"url":3221,"score":3222},"**Describe the bug**\nWhen submitting whitespace-only input (space) in these fields: \n- **Encounter Page** → Notes section \n- **Resource Requests** → Reason for Request field \n\nThe system accepts it as valid input, creating: \n- Empty notes that clutter the UI \n- Resource requests with blank reasons\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to encouter page or resource request page\n2. Click on Add Allergy, Add Diagnosis, and Add Symptom or reason of request section\n3. Just enter a space and submit\n4. See error\n\n**Expected behavior**\nUser should not be able to create empty notes, Also reason of request is not supposed to by bypassed with a whitespace.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/f992b635-b1de-400c-9363-9c483b2f2623\n\n\n\n\n\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",[3214],{"name":3215,"color":3216},"stale","688388",12621,"closed","Entering just whitespace in input fields still creates empty entries","2025-07-29T20:22:14Z","https://github.com/ohcnetwork/care_fe/issues/12621",0.6351221,{"description":3224,"labels":3225,"number":3226,"owner":3172,"repository":3173,"state":3218,"title":3227,"updated_at":3228,"url":3229,"score":3230},"**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.6472918,{"description":3232,"labels":3233,"number":3234,"owner":3172,"repository":3173,"state":3218,"title":3235,"updated_at":3236,"url":3237,"score":3238},"**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.66568565,{"description":3240,"labels":3241,"number":3245,"owner":3172,"repository":3173,"state":3218,"title":3246,"updated_at":3247,"url":3248,"score":3249},"**Description:**\nTextArea in the Appointment Question is not accepting white spaces while typing.\n\n**Expected Behaviour**\nSpaces should be allowed so users can enter complete sentence.",[3242],{"name":3243,"color":3244},"P1","519BFE",12673,"Unable to Enter Spaces in Appointment Question Reason for visit field","2025-06-20T18:29:24Z","https://github.com/ohcnetwork/care_fe/issues/12673",0.67237395,{"description":3251,"labels":3252,"number":3253,"owner":3172,"repository":3173,"state":3218,"title":3254,"updated_at":3255,"url":3256,"score":3257},"**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.6815167,["Reactive",3259],{},["Set"],["ShallowReactive",3262],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fLBRbkUTGCyzisEb8o6JK0NWveJ6UD4f4rvfRZgEdllk":-1},"/ohcnetwork/care_fe/13025"]