saleor-dashboard-feedback
Skill1.1k starsChanged 8 days agoBSD-3-ClauseView on GitHub
Rules for surfacing errors, warnings, and success feedback in Saleor Dashboard (Geist/Vercel-aligned). Use when adding useNotifier/toasts, save/mutation error handling, form validation, banners, setup blockers, or dogfooding feedback quality on entity views (vouchers first). Covers when to toast vs inline vs persistent UI, toast copy quality, stickiness, and anti-patterns.
Trending
Less talk lately.about the whole repository
Who's talking about saleor/saleor-dashboard
- saleor/saleor“Unable to update Company info from Dashboard”GitHub · May 31, 2022 · 2 reactions
- saleor/apps“Implement logo field in AppManifest”GitHub · Feb 22, 2023 · 1 reactions
- saleor/saleor“Support for payment transaction actions”GitHub · Aug 11, 2022 · 1 reactions
- saleor/saleor“feat(attribute): add staff-only internalDescription to Attribute”GitHub · Oct 15, 2026
- waelhe/app-java-v3“docs(admin): plan Saleor Dashboard adaptation for marketplace”GitHub · Oct 15, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- May 31, 2022Unable to update Company info from Dashboard — saleor/saleor2 reactions · 3 comments
- Feb 22, 2023Implement logo field in AppManifest — saleor/apps1 reaction · 3 comments
- Aug 11, 2022Support for payment transaction actions — saleor/saleor1 reaction · 27 comments
- Oct 15, 2026feat(attribute): add staff-only internalDescription to Attribute — saleor/saleor0 reactions · 1 comment
- Oct 15, 2026docs(admin): plan Saleor Dashboard adaptation for marketplace — waelhe/app-java-v30 reactions · 3 comments
45 more on GitHub
- Jul 31, 2026feat(avatax): add tax code action to Dashboard command palette — saleor/apps0 reactions · 5 comments
- Jul 13, 2026Add reason for price override — saleor/saleor0 reactions · 1 comment
- Jul 8, 2026Improved Gift Card APIs — saleor/saleor0 reactions · 1 comment
- Jun 9, 2026[Feature] Support pasting boolean values in other that English — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026Fix Background task provider tests — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Missing filter when calling exportGiftCards mutation for selected giftcards — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Variant view, no scroll on warehouse list and only first 50 warehouses displayed for the user — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: `requestPasswordReset` mutation returns incorrect error when user is not staff user — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Missed info about no access to the channels — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026 `create order` button should be disabled in case of no permissions — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026User can create group with permission from plugin but cannot assign members via UI — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Enhancement]: Misleading UI when charge is pending — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Modal leave without saving after logout — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Feature]: Change navigation structure — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Only first 50 warehouses are loaded in the grid — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Weight rate create - not consistent error messages — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Price rate and weight base availability button inactive — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Changing attribute value on product triggers SKU fail — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Restrict order weight in shipping method not saved — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Datagrids jump to end when resizing column — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Enable refunding specific product lines — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Deleting variant attribute changes variant name — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Column picker refinement — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026No information about required fields in product variant form — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Error handling in product variant page - user can delete required field and still be able to save - then success banner shows up followed by error banner — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Remove add product — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Not all attributes are validated — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Error label misplaced — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Error messages missmatch — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Epic]: Improve UX flow for order refunds using Transactions API — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Can not refund fulfilled order — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Incorrect background in label cell — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: City and Postal code is getting cleared while modifying and saving the country field and country area in warehouse modification — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]:Error displayed while selecting Category name header checkbox and click pagination in category Listing Page — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: dashboard not using all settings field in query (Can't set limitQuantityPerCheckout) — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 3, 2026Add support for editorJS table syntax — saleor/saleor0 reactions · 1 comment
- May 5, 2026HOMEPAGE_WIDGETS types for manifest — saleor/app-sdk0 reactions · 2 comments
- Mar 25, 2026Fix LSP not loading `.js` and `.ts` files correctly — graphql/graphiql0 reactions · 5 comments
- Mar 13, 2026Add proper gift card events when gift card is used as a payment method — saleor/saleor0 reactions · 1 comment
- Mar 12, 2026Fix smoke tests - add prefix for artifact upload — saleor/apps0 reactions · 3 comments
- Mar 6, 2026Introduce password login mode — saleor/saleor0 reactions · 2 comments
- Mar 5, 2026Add SaleorGiftcardPaymentMethodDetails to transaction — saleor/saleor0 reactions · 2 comments
- Feb 25, 2026Fix failing smoke tests workflow — saleor/apps0 reactions · 3 comments
- Feb 13, 2026document payment method details in dashboard — saleor/saleor-docs0 reactions · 1 comment
- Feb 10, 2026Refund reasons phase 2 (POC) — saleor/saleor0 reactions · 1 comment
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- pinactSkill
- saleor-dashboard-cloud-extensionsSkill
- saleor-dashboard-detail-pagesSkill
- saleor-dashboard-entity-detailSkill
- saleor-dashboard-formsSkill
- saleor-dashboard-github-workflowsSkill
- saleor-dashboard-graphql-batchingSkill
- saleor-dashboard-listsSkill
- saleor-dashboard-loadingSkill
- saleor-dashboard-microcopySkill
- saleor-dashboard-pr-quality-checkSkill
- saleor-dashboard-security-auditSkill
- saleor-dashboard-smooth-shadowSkill
- saleor-dashboard-stylesSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
If a toast is the only place the full error exists, the design is wrong.
- Distinctive: line 46
Never: use a toast alone for: billing/permission denials, multi-step triage, field validation, or setup blockers.
- Very specific: line 100
Prefer existing commonMessages / feature messages over one-off strings.
- Distinctive: line 106
Default: title only, or title + ≤ 2 short lines of description.
- Very specific: line 108
If the full message needs reading time, it belongs in a banner/dialog/checklist, not the toast.
- Very specific: line 134
Prefer explicit title; don’t lean on generic “Error” / “Success” defaults for product flows.
- Very specific: line 159
Use this skill when touching src/discounts/ voucher create/details/list.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Saleor Dashboard Feedback
How merchants learn that something worked, failed, or needs attention — without offloading triage into toasts.
Inspired by Geist Toast and Vercel product UI
discipline. Implement with macaw-ui-next + useNotifier / our toast queue — do not
install Geist packages.
Also see: saleor-dashboard-entity-detail
(page anatomy), saleor-dashboard-microcopy
(hint copy), toast implementation under src/components/notifications/.
Principle
Feedback lives next to the problem when the merchant must act. Toasts acknowledge terminal, non-blocking outcomes of an action they just took.
If a toast is the only place the full error exists, the design is wrong.
Channel ladder (pick the lowest that fits)
| Channel | When | Stays until | Examples |
| Inline field | A specific input is invalid | Field corrected / next submit | Required code, bad date, amount out of range |
| Section / card error | Error belongs to a settings block or list row | Next successful save or explicit dismiss | Rule form error border, codes table row failure |
| Page banner / alert | Page-level blocker or recovery path the merchant must see while on the page | Condition clears or dismiss | Permission denied, channel not ready, conflict on load |
| Setup checklist | Readiness / configuration funnel | Step completed | Missing requirements before activate |
| Toast | Non-blocking ack of a user-initiated action | Auto (~5s) or sticky if error/action | “Changes saved”, “Couldn’t delete code. Try again.” |
| BackgroundTasks | Long-running job | Task UI | Exports, bulk ops |
Never use a toast alone for: billing/permission denials, multi-step triage, field validation, or setup blockers.
When to use a toast
Do toast
- Success after Save / create / delete / assign the merchant just triggered
- Short failure of that same action when the page already shows context (or a one-line recovery is enough)
- Undo-style confirmations with a single action (
Undo) - Terminal state of an async flow (one toast at the end — not start/middle/end)
Do not toast
- Narrating a multi-step mutation sequence (
Saving…→Validating…→Saved) - Dumping raw GraphQL / API payloads or stack traces
- Repeating the same error on every keystroke or every failed field
- Anything the merchant must still fix on this page without a matching inline/banner home
- N toasts for N row failures — aggregate (
3 codes couldn’t be deleted)
Pairing rule (Geist)
For serious failures, prefer:
- Short toast (≤ ~6 words in the title sense):
Couldn’t save voucher - Persistent surface with the recovery step and enough identity to act
Toast: Couldn’t save voucher
Page: banner or field — “End date must be after start date.”Toast quality bar
Our queue: max 3 visible, FIFO overflow, dedupe by status + title, dismiss-visible
only when 2+ show. Errors and actionBtn stay until dismissed
(getNotificationDuration → Infinity). See notificationQueue.tsx.
Copy
| Kind | Shape | Example |
| Success | {Noun} {past-participle} — no “successfully” | Voucher saved, Codes deleted |
| Neutral / cancel | Past tense of what happened | Export canceled |
| Error | What failed + recovery (two short sentences OK) | Couldn’t delete codes. Try again. |
| Warning | Risk or partial outcome, still scannable | Some codes were skipped |
- Sentence case. Single-sentence success: no trailing period.
- Error: use Couldn’t for user/state issues; Failed to for system/infra — stay consistent in one flow.
- Match the button verb: Delete →
… deleted, not… removed. - Title carries the punch; description is optional context — not a paragraph.
- Prefer existing
commonMessages/ feature messages over one-off strings.
Length
Sonner/Geist do not ship show-more. Canonical fix is shorter copy.
- Default: title only, or title + ≤ 2 short lines of description.
- Our Toast clamps long descriptions (2 lines + chevron) as a safety net for legacy/API text — do not rely on it for new work.
- If the full message needs reading time, it belongs in a banner/dialog/checklist, not the toast.
Behavior
| Status | Auto-dismiss | Notes |
| success / info / warning (no action) | ~5s (DEFAULT_NOTIFICATION_SHOW_TIME) | Pauses on hover |
| error | Sticky until dismiss | Default; don’t preempt other toasts |
error + explicit autohide | That duration | Use when field/section already owns recovery (paired ack); prefer PAIRED_ERROR_NOTIFICATION_SHOW_TIME (~10s) for save/create failures |
any + actionBtn | Sticky until dismiss or action | One clear action label; wins over autohide |
- One terminal toast per user action.
- Deduping replaces same
status + title— update description if the detail changed; don’t spam. - Bulk: one aggregated notify, not a toast per row.
useNotifier checklist
notify({
status: "success", // or error | warning | info
title: intl.formatMessage(messages.voucherSaved), // prefer explicit title
// text: optional short description
// actionBtn: only when a single recovery/undo is real
});- Prefer explicit
title; don’t lean on generic “Error” / “Success” defaults for product flows. - Pass
actionBtnonly for a safe, single next step (Undo, Open settings) — not primary navigation dumps. - On save failure: map GraphQL errors to fields/sections first; toast is the ack, not the encyclopedia.
Decision tree
Did the merchant just complete an action?
no → persistent UI only (banner / checklist / empty state). No toast.
yes → Did it succeed?
yes → success toast (short). Done.
no → Can they fix it on a specific field/section?
yes → inline/section error + short error toast (optional if inline is obvious).
no → Is it a page-level / permission / readiness issue?
yes → banner or checklist + short error toast.
no → short sticky error toast with recovery sentence;
file a follow-up if this keeps happening (wrong surface).Dogfood: vouchers (first)
Use this skill when touching src/discounts/ voucher create/details/list.
Audit checklist
- Save success → one
Voucher saved/Changes savedtoast; no second toast from the same submit - Field validation (dates, limits, codes) → inline / section errors; toast does not carry the full validation list
- Code bulk delete / generate failures → aggregated toast; row/section detail if the merchant must retry specifics
- Permission / channel blockers → banner or checklist, not toast-only
- No toast on every codes-table refetch or filter change
- Error toast copy: couldn’t/failed + recovery; sticky by default (or
autohidewhen paired with inline/section); no raw API blob intext - Action buttons on toasts only for real undo/recovery (not “Close”)
Anti-patterns to remove when found
// ❌ Toast-only validation
notify({ status: "error", text: errors.map(e => e.message).join(", ") });
// ❌ Narrating the flow
notify({ status: "info", text: "Saving voucher…" });
notify({ status: "success", text: "Voucher saved successfully." });
// ✅ Terminal ack + inline home for the problem
form.setError("endDate", { message: intl.formatMessage(messages.endBeforeStart) });
notify({
status: "error",
title: intl.formatMessage(messages.couldNotSaveVoucher),
text: intl.formatMessage(messages.checkHighlightedFields),
autohide: PAIRED_ERROR_NOTIFICATION_SHOW_TIME,
});Implementation map
| Concern | Where |
| Notify API | src/hooks/useNotifier/useNotifier.tsx |
| Duration / sticky rules | src/hooks/useNotifier/utils.ts |
| Queue (cap 3, FIFO, dedupe) | src/components/notifications/notificationQueue.tsx |
| Toast UI (clamp safety net) | src/components/notifications/Toast.tsx |
| Common success/error strings | src/intl.ts, src/utils/errors/common.ts |
Restraint tests
Before shipping feedback:
- Squint test — can you tell success vs failure in under a second?
- Absent-toast test — if the toast never appeared, could the merchant still recover from on-page UI?
- Tall-toast test — if description needs show-more, shorten the copy or move it out of the toast.
- Stack test — would a slow merchant still see the important message with max 3 + FIFO? If not, it shouldn’t be toast-only.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

