Fix [object Object] bugs in note page + add favicon #12

New issue

Closed

opened 2026-03-14 13:36:39 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-14 13:36:39 +00:00

Owner

Lineage

plan-pal-e-docs → Phase 4 → Phase 4c (E2E bug fixes)

Repo

forgejo_admin/pal-e-app

User Story

As a user browsing notes
I want to see correct project names and tag names in the UI
So that navigation works and the page doesn't show [object Object]

Context

Playwright E2E testing against the live deployment (pal-e-app.tail5b443a.ts.net) found two rendering bugs on the note detail page. The API returns objects for project and tags, but the Svelte template renders them as strings.

File Targets

src/routes/notes/[slug]/+page.svelte — fix breadcrumb project link and tag rendering
src/routes/notes/[slug]/+page.server.ts — may need to extract project slug/name before passing to page
static/favicon.png — add a favicon (or static/favicon.ico)

Acceptance Criteria

Breadcrumb shows project name and links to /projects/{project.slug} (not /projects/[object Object])
Tag badges show tag name and link to /tags/{tag.name} (not /tags/%5Bobject%20Object%5D)
No [object Object] anywhere in rendered pages
No 404 console error for favicon
npm run check && npm run build passes

Test Expectations

Run command: npm run check && npm run build

Constraints

The API returns project as {"slug": "...", "name": "...", ...} and tags as [{"id": N, "name": "..."}]
Access .slug and .name properties explicitly — don't rely on string coercion

Checklist

PR opened
Tests pass
No unrelated changes

Closes #12

pal-e-docs — project

### Lineage `plan-pal-e-docs` → Phase 4 → Phase 4c (E2E bug fixes) ### Repo `forgejo_admin/pal-e-app` ### User Story As a user browsing notes I want to see correct project names and tag names in the UI So that navigation works and the page doesn't show `[object Object]` ### Context Playwright E2E testing against the live deployment (`pal-e-app.tail5b443a.ts.net`) found two rendering bugs on the note detail page. The API returns objects for `project` and `tags`, but the Svelte template renders them as strings. ### File Targets - `src/routes/notes/[slug]/+page.svelte` — fix breadcrumb project link and tag rendering - `src/routes/notes/[slug]/+page.server.ts` — may need to extract project slug/name before passing to page - `static/favicon.png` — add a favicon (or `static/favicon.ico`) ### Acceptance Criteria - [ ] Breadcrumb shows project name and links to `/projects/{project.slug}` (not `/projects/[object Object]`) - [ ] Tag badges show tag name and link to `/tags/{tag.name}` (not `/tags/%5Bobject%20Object%5D`) - [ ] No `[object Object]` anywhere in rendered pages - [ ] No 404 console error for favicon - [ ] `npm run check && npm run build` passes ### Test Expectations - Run command: `npm run check && npm run build` ### Constraints - The API returns `project` as `{"slug": "...", "name": "...", ...}` and `tags` as `[{"id": N, "name": "..."}]` - Access `.slug` and `.name` properties explicitly — don't rely on string coercion ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes Closes #12 ### Related - `pal-e-docs` — project