To Review
Items flagged during setup that need a deliberate decision. Do not act on these without confirming the right answer first.
.claudeignore — uncertain paths
The following paths were identified as candidates for .claudeignore but were left out pending confirmation from the project owner:
| Path | Reason for uncertainty |
|---|---|
django-api/media/ | Uploaded user files — likely safe to ignore, but confirm no fixture or test data lives here |
django-api/locale/ | i18n .po/.mo files — not useful for AI to read, but harmless if included |
django-api/novahomecareapi/fixtures/ | JSON seed data — could be useful context for understanding the data model, or noise depending on how large it grows |
Once decided, update .claudeignore at the repo root and remove the entry from this table.
drf-spectacular schema generation errors
On every startup, three views fail to introspect cleanly during schema generation:
| View | Error |
|---|---|
FormViewSet (job_forms/views.py) | 'AnonymousUser' object has no attribute 'is_admin' |
ContactFormView (support/views.py) | 'Request' object has no attribute 'organization' |
PingView (utils/healthcheck.py) | Unable to guess serializer |
These are non-fatal — drf-spectacular skips them and the server starts. However, the OpenAPI schema will be missing or incomplete for these endpoints. The fix likely involves adding @extend_schema decorators or providing a serializer_class that doesn't depend on a live request, but this is third-party code — needs proper investigation before touching.
Brittle Chakra UI selector in login tests (3 failing)
cypress/pages/Login/login.js uses this selector to verify successful login:
roleTitle: () => cy.get('p.chakra-text.css-6q9ebm'),css-6q9ebm is a generated Chakra UI class — it changes whenever the component tree or theme config changes. On the first run of the login tests (18 Jan 2026), 3 tests failed because this class no longer exists in the current build:
| Test | Feature file |
|---|---|
| Verify user enters portal after correct login | log_in_21.feature |
| Login successful | login.feature |
| Login successful | log_in_24.feature |
The fix is to replace the selector with a stable data-cy attribute on the role title element in the portals source, then update the page object. Needs investigation into what the role title element looks like in the current portals build before touching either file.
HTTPS=true in portals/.env
The portals .env.development.example contains HTTPS=true, a leftover from the previous Create React App setup. Vite ignores this variable. Confirm it can be removed from the example file to avoid confusion.