ideasbugs 0.9.0 → 0.10.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 722346f32d21b2a7007ffb9b04aeda8bf66e8194dc3eaa544bc3ea4bbdb2fe47
-  data.tar.gz: ca6574200a4e00570ed5a26aa9f4ed758c06192789336f4852622766b471fb5e
+  metadata.gz: 383c2bf2c3fc0168a96e1e418398bc643b19c4364440604912d1e546543fc62a
+  data.tar.gz: c40e84232ccc55b2394adbe9421f297a3c93e6cdff98c8d31e50f7c40e8e9148
 SHA512:
-  metadata.gz: aede97be97f27ce8e4cb615efc2e4ffb864ac7b1a7d09a1c6dc67fe2429a2ebb42cc01b2e65541d41a4a2908406fef9d6a90ae886a1e87ce93d78e51f3ca9d30
-  data.tar.gz: e1266b1bd43e2a14b5ad92c1fd1f29752bb13ee925d46a1a5939dc9ec3570d625b0d49b8e6de3d17e7cb054e4d066e86493abc8ec26043c567aa6062ffb06ed5
+  metadata.gz: 32f3a5e503b09ae996a87890f4aceb11ab337db5bae30a711d019d834e1a639ee985e7a71cb380038d7ef2799e3df4d5b9e4d06b686021ac19bab7411ad1c329
+  data.tar.gz: 0d11c01642ba6dea041d336461bcb69a65184190dcc28d544ca605a6827107a4fa7729f36fb71865ab6c07d251d4f3ae4af912feed8ac790614ed757778005a2

data/AGENTS.md

@@ -177,6 +177,6 @@ Conventions this codebase holds to — follow them rather than the first thing t
 - **Attachments stream through the engine's gate**, never a public blob URL.
 - **The widget is plain JS served same-origin by the engine** — no build step, no framework.
 - **The dummy app pins `config.active_job.queue_adapter = :test`.** Do not remove it or let it drift back to the `:async` default. Attaching a screenshot enqueues Active Storage's analysis job, and `:async` runs it on a background thread that checks out its own connection — writes no test transaction covers, landing in the middle of whatever runs next. That is a suite that fails order-dependently in a test which never created a row, and it is miserable to trace back.
-- **`lib/ideasbugs/dashboard.css` is half shared.** Everything above the `GEM-SPECIFIC` banner is the design system all five gems in the family ship — the same tokens, the same `.page-head`/`.tabs`/`.filters`/`.card`/`.badge`/`button`, the same `.dashboard-shell` + `.record-row` + `.detail-panel` two-pane dashboard — identical in every repo apart from the `ib` prefix. Diff it against a sibling before changing it, and carry the change to the other four. Anything only this gem has goes below the banner. New dashboard markup reuses the shared class names rather than inventing a domain-specific one.
+- **`lib/ideasbugs/dashboard.css` is half shared.** Everything above the `GEM-SPECIFIC` banner is the design system all five gems in the family ship — the same tokens, the same `.page-head`/`.tabs`/`.filters`/`.card`/`.badge`/`button`/`.status-switch`, the same `.dashboard-shell` + `.record-row` + `.detail-panel` two-pane dashboard — identical in every repo apart from the `ib` prefix. Diff it against a sibling before changing it, and carry the change to the other four. Anything only this gem has goes below the banner. New dashboard markup reuses the shared class names rather than inventing a domain-specific one.
 - Every user-facing change bumps `lib/ideasbugs/version.rb` and adds a `CHANGELOG.md` entry that says what it costs, not only what it adds.
 - Commit messages are prose that explains the tradeoff — read `git log` before writing one.

data/CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## 0.10.0
+
+- **Triage is one switch now.** Open, In review and Resolved sit in a single pill
+  in the panel heading — the status the report is in is lit in that status's
+  colour, the other two are one click away. It replaces the row of `Mark in
+  review` / `Mark resolved` / `Reopen` buttons under the message, which grew a
+  button per status and read as three unrelated actions rather than one control.
+  The status badge left the heading with them: the switch already says it.
+- **The switch is the family's, not this gem's.** It lives in the shared core of
+  `dashboard.css` as `.status-switch`, the same component livechat's
+  open/resolved switch now uses, so a third gem that needs one inherits it.
+- No JavaScript: each segment is a submit button in one form, and the lit segment
+  is a `type="button"` so clicking the status a report already has cannot re-file
+  it. If you styled the old `.actions` status buttons, that is the breaking
+  change — `PATCH /feedbacks/:id` with `feedback[status]` is unchanged, so any
+  script or link that drove triage still works.
+
 ## 0.9.0
 
 - **One design system across the family.** The stylesheet now opens with a

data/app/views/ideasbugs/feedbacks/_feedback_panel.html.erb

@@ -4,11 +4,25 @@
       <span class="badge kind-<%= feedback.kind.to_s.parameterize %>">
         <%= t("ideasbugs.kinds.#{feedback.kind}", default: feedback.kind.humanize) %>
       </span>
-      <span class="badge status-<%= feedback.status %>">
-        <%= t("ideasbugs.statuses.#{feedback.status}", default: feedback.status.humanize) %>
-      </span>
       <span class="case-id">#<%= feedback.id %></span>
     </h1>
+
+    <%# The shared status switch, carrying the status the heading badge used to
+        state: the current one is lit and inert, every other one is a submit
+        that files the report under it. One form, no JS. %>
+    <%= form_with url: feedback_path(feedback), method: :patch, class: 'status-switch' do %>
+      <% Ideasbugs::Feedback::STATUSES.each do |status| %>
+        <% label = t("ideasbugs.statuses.#{status}", default: status.humanize) %>
+        <% if status == feedback.status %>
+          <button type="button" class="status-<%= status %> current" aria-current="true"><%= label %></button>
+        <% else %>
+          <button name="feedback[status]" value="<%= status %>" class="status-<%= status %>"
+                  aria-label="<%= t("ideasbugs.dashboard.move_to_#{status}", default: "Mark #{status.humanize.downcase}") %>">
+            <%= label %>
+          </button>
+        <% end %>
+      <% end %>
+    <% end %>
   </div>
 
   <div class="detail-scroll">
@@ -49,13 +63,9 @@
       <% end %>
     </div>
 
+    <%# Status lives in the switch in the heading; only what a switch cannot say
+        is left here. %>
     <div class="actions">
-      <% (Ideasbugs::Feedback::STATUSES - [feedback.status]).each do |status| %>
-        <%= button_to t("ideasbugs.dashboard.move_to_#{status}", default: "Mark #{status.humanize.downcase}"),
-                      feedback_path(feedback),
-                      method: :patch, params: { feedback: { status: status } },
-                      class: ('primary' if status == 'resolved') %>
-      <% end %>
       <%= button_to t('ideasbugs.dashboard.delete', default: 'Delete'),
                     feedback_path(feedback),
                     method: :delete, class: 'danger',

data/lib/ideasbugs/dashboard.css

@@ -144,6 +144,19 @@
   & .actions form { display: inline; }
   & .form-actions { padding-top: 12px; }
 
+  /* Status switch: one pill holding every state a record can be in, the state it
+     is in now lit. Each other segment is a submit button, so moving a record
+     takes one click and no JavaScript; the current segment is a `type="button"`
+     so clicking it cannot re-file the record it is already filed under. Two
+     states or five, the pill sizes itself. A gem tints the lit segment with its
+     own status colour — see the `GEM-SPECIFIC` section. */
+  & .status-switch { display: inline-flex; flex: 0 0 auto; margin: 0; padding: 3px; border: 1px solid var(--ib-border); border-radius: 999px; background: var(--ib-bg); }
+  & .status-switch button { min-height: 30px; padding: 0 12px; border: 0; border-radius: 999px; background: none; color: var(--ib-muted); font-size: 13px; font-weight: 700; white-space: nowrap; transition: background .16s ease, color .16s ease; }
+  & .status-switch button:hover { border: 0; background: color-mix(in srgb, var(--ib-muted) 12%, transparent); color: var(--ib-text); }
+  & .status-switch button.current { background: var(--ib-surface); color: var(--ib-text); box-shadow: 0 1px 2px rgba(15, 23, 42, .12); cursor: default; }
+  & .status-switch button.current:hover { background: var(--ib-surface); }
+  & .panel-head .status-switch { margin-left: auto; }
+
   & .card { overflow: hidden; border: 1px solid var(--ib-border); border-radius: 12px; background: var(--ib-surface); }
   & .card.pad { padding: 16px; overflow: visible; }
   & table { width: 100%; border-collapse: collapse; }
@@ -266,6 +279,7 @@
     & .dashboard-detail .detail-panel { min-height: calc(100vh - 64px); }
     & .mobile-back { display: block; flex: 0 0 auto; margin: 4px 0 10px; font-size: 13px; }
     & .panel-head h1 { font-size: 18px; }
+    & .status-switch button { padding: 0 9px; font-size: 12px; }
     & dl { grid-template-columns: 1fr; gap: 3px; }
     & dd { margin-bottom: 8px; }
   }
@@ -294,6 +308,12 @@
   & .badge.status-in_review { background: var(--ib-in-review); }
   & .badge.status-resolved { background: var(--ib-resolved); }
 
+  /* The lit segment of the status switch carries the same colour as the badge
+     for that status, so the panel and the queue agree at a glance. */
+  & .status-switch button.current.status-open { color: var(--ib-open); }
+  & .status-switch button.current.status-in_review { color: var(--ib-in-review); }
+  & .status-switch button.current.status-resolved { color: var(--ib-resolved); }
+
   & .shots { display: flex; gap: 12px; flex-wrap: wrap; margin-top: 8px; }
   & .shots img { max-width: 280px; max-height: 200px; border: 1px solid var(--ib-border); border-radius: 8px; }
 }

data/lib/ideasbugs/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Ideasbugs
-  VERSION = '0.9.0'
+  VERSION = '0.10.0'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ideasbugs
 version: !ruby/object:Gem::Version
-  version: 0.9.0
+  version: 0.10.0
 platform: ruby
 authors:
 - Yaroslav Shmarov