4 Commits

Include renames

Author	SHA1	Message	Date
bermudalambandClaude Opus 5	d28fb5634a	feat(ui): storefront filters and admin category/tag management (#23) ... Storefront gains a Filters drawer holding the category tree, colour-coded tag pills, and a price range, with applied filters shown as removable chips. Filter state lives in the URL query string, so a filtered view is shareable and the back button works. Item cards now show their category and tags. Admin gains Categories and Tags tabs, and the item form gains a category TreeSelect plus a tags Select that creates new tags on the fly. The admin category tree tracks expansion in state rather than using defaultExpandAll: that prop is evaluated once at mount, so a branch added afterwards rendered collapsed and its children were unreachable. Creating or moving a node now expands its parent. Caught by the new admin e2e spec. The chip row is marked as a named group so its "Clear all" stays distinguishable from the drawer's. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-17 09:34:37 -05:00
bermudalambandClaude Opus 5	a240d86762	test: disambiguate the Email locator in auth.spec ... getByLabel('Email') matched two elements on /register -- the email input and the marketing consent checkbox, whose label "Send me occasional emails" contains the substring. Playwright's strict mode failed both tests that filled it. getByRole('textbox', ...) narrows by role, so the checkbox no longer collides. Applied to the /login usage too, so the same concept reads the same way throughout the file. These failures were latent: the frontend-e2e job died at the build step before it ever reached the tests, so CI never reported them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-15 18:35:43 -05:00
bermudalambandClaude Opus 5	b7c8c37447	fix: add the missing /verify-email page ... Verification emails linked to /verify-email?token=..., but no such route existed in main.tsx and nothing in the frontend ever called POST /api/customers/verify-email. The SPA catch-all served index.html, no route matched, and the page rendered blank -- so the token was never redeemed and accounts stayed unverified forever. The gap was invisible until SMTP was configured, because no verification email had ever actually been delivered. Adds VerifyEmail.tsx (verifying / verified / failed states), a verifyEmail call in customerApi, and the route. The request is pinned to a single firing via a ref: the endpoint deletes the token on success, so StrictMode's double effect invocation in dev would otherwise overwrite the success state with "invalid or expired token". Verified end to end against a local stack: a real token flips customers.email_verified to true and is consumed from customer_tokens. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-15 18:16:32 -05:00
bermudalamb	921022c658	Add backend unit/integration tests, Playwright e2e tests, README, cookie Secure fix	2026-08-13 22:35:38 +00:00