ohcnetwork/care_fe

Describe the bug On an encounter's Plots tab, every chart (Blood Pressure, Pulse, Temperature, GRBS, etc.) renders an empty graph with blank axes when the patient has no recorded observations for those codes. The "No data available" empty state that exists in ObservationVisualizer never shows. The empty state is only shown when data.results is an empty array (src/components/Common/Charts/ObservationChart.tsx, if (!data?.results?.length)). But the observation/analyse/ endpoint always returns one entry per requested code, with an empty inner results array when there is no data: { "results": [ { "code": { "code": "8480-6", "display": "Systolic", ... }, "results": [] }, { "code": { "code": "8867-4", "display": "Pulse", ... }, "results": [] } ] } So data.results.length is never 0 and the check never triggers. The same happens per chart: if one chart in a tab has data and another doesn't, the empty one still draws blank axes. To Reproduce Log in as care-doctor (local backend wit

Context #16462 adds src/components/ui/responsive-dialog.tsx — one component that renders a bottom sheet on mobile and a centered dialog on desktop behind a single API. It is currently used in one place (ServiceRequestShow). The same fork is hand-written in 9 other components. This issue tracks migrating them. Problem Each site writes its container twice — once for mobile, once for desktop — with the title, description and body duplicated across both branches. The two copies drift: a prop added to one branch and not the other is invisible in review, and the bug only shows on one screen size. Container forks on develop today: File Mobile Desktop src/components/Common/RequirementsSelector.tsx:340 Drawer Popover src/components/Common/ResourceDefinitionCategoryPicker.tsx:794 Drawer Popover src/components/Common/RoleOrgSelector.tsx:293 Drawer Popover src/components/Patient/PatientIdentifierFilter.tsx:506 Drawer Popover src/components/Tags/MultiFilterStyleTagSelector.tsx:

Describe the bug When the backend responds with HTTP 413 (Content Too Large), the global error handler shows a toast using t("file_too_large") (src/Utils/request/errorHandler.ts:26-29). That key is missing from public/locale/en.json, so the toast shows the raw key file_too_large instead of a readable message. The key was added in #15469 ("Handled HTTP 413 error"). Two days later, #15491 ("Prescription note", commit 31ce4cd) removed it, apparently by accident. Nothing else defines it. I found this by reading the code, not by seeing it in the UI. Running i18next with the current en.json gives: t("file_too_large") -> "file_too_large" t("not_found") -> "Not Found" To Reproduce Steps to reproduce the behavior: Send a request the server rejects with HTTP 413, such as a file upload larger than the proxy or server size limit. handleHttpError catches the 413 and calls toast.error(t("file_too_large")). The toast should display the raw key file_too_large, based on the code and the i18next

Overview This issue tracks incremental improvements to Playwright E2E test coverage for the CARE frontend. Each weekday, a new test or improvement is added via draft pull request. Coverage Landscape Well-Covered Areas ✅ Authentication flows (login, logout, session management) Patient management (registration, home page, encounters) Facility billing & payments Facility settings (devices, locations, departments, products, services) Encounter workflows (notes, medicines, service requests, structured questions) Admin operations (roles, tags, value sets, questionnaires) Organization management Queues and token management Profile pages Coverage Gaps (Priority Order) 🔴 Appointments System (HIGH - User-facing healthcare workflow) AppointmentList (started 2026-09-04) AppointmentDetail BookAppointment flows Appointment scheduling Scheduling System (HIGH - Healthcare operations) Schedule templates Schedule exceptions Patient History Pages (MEDIUM - Clinical reference) All

Overview Systematic tracking of Playwright E2E test coverage improvements for the CARE frontend application. This issue serves as a central hub for documenting coverage gaps and improvements made during daily runs. Coverage Status Summary Coverage by Module Module Coverage Status Priority Appointments 0% ❌ No tests HIGH Admin/Roles ✅ Complete Active - Admin/Tags ✅ Complete Active - Facility/Patients ✅ Complete Active - Facility/Encounters ✅ Complete Active - Facility/Billing ✅ Complete Active - Facility/Users ✅ Complete Active - Organization ✅ Complete Active - Auth/Login ✅ Complete Active - Current Statistics Total Test Files: 96 New Coverage Added: Tests for Appointments List Page Remaining Gaps: Appointments detail view Appointments booking flow Public appointments module Scheduling (slots/queues beyond basic coverage) Improvement Log 2026-09-03 - Initial Appointments Coverage PR: (See linked PR in automation) What was improved: Adde