Add "request a datalogger" contact category + logger-picker button#321
Merged
Conversation
|
Updates to Preview Branch (feature/request-loggers-contact) ↗︎
Tasks are run on every commit but only new migration files are pushed.
View logs for this Workflow Run ↗︎. |
Coverage SummaryLines: 58.57% (6343/10829) · Statements: 57.5% · Functions: 55.89% · Branches: 53.45% Per-file coverage
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
lapwing | c53b7fa | Commit Preview URL Branch Preview URL |
Jun 30 2026, 03:34 AM |
- New contact-form category "New Datalogger Connection" (ContactDialog + submit-message ALLOWED_CATEGORIES + admin MessagesTab map/colour + i18n). - ContactDialog gains optional `trigger` and `defaultCategory` props so it can be opened from elsewhere with a category preselected. - LoggerPicker: a "Request additional dataloggers" button under the logger tiles opens the contact form pre-set to the new category — so users confused about why a native app is needed (e.g. Alfano) have an obvious way to ask for more loggers. i18n across all locales + CHANGELOG. Green: lint, typecheck, 2086 tests, build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VUypCCbFtY85CaHxj9VWE6
TheAngryRaven
force-pushed
the
feature/request-loggers-contact
branch
from
af023d9 to
c53b7fa
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A small addition for the v3.0.0 release: an easy way for users to ask for support for a logger that isn't listed.
ContactDialog, thesubmit-messageedge function'sALLOWED_CATEGORIES(so the backend accepts it), and the admin MessagesTab (display label + colour).ContactDialogis now openable preselected — it gained optionaltriggeranddefaultCategoryprops.Type of Change
Checklist
bun run lint/typecheck/test:run(2086) /buildpasslanding+admin, button inlogger)Notes for Reviewers / release ordering
[2.10.0]) unreleased Added section — a region the release-prep PR Release prep v3.0.0 #320 doesn't touch, so the two merge cleanly; once both land, the bullet sits under[3.0.0].submit-messageedge function change must deploy for the new category to be accepted (Supabase auto-deployssupabase/functions/**).bun run i18n:seedto translate.🤖 Generated with Claude Code
Generated by Claude Code