user-feedback: cache verification missed non-default purchase situations
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- supabase
- Domain
- documentation
Research direction
Open SKILL.md and read Core Principles > 2. Verify your work. Expand the checklist for third-party API caches to cover pagination, date filters, statuses or situations, grouped counts, duplicates, exclusions, and reconciliation against the source UI or an independent aggregate. Done means the guidance prevents a default or partial response from being described as a complete cache load.
Written by the indexing model from the issue text.
Description
What happened
Task: Build and validate a 12-month Supabase cache for purchases imported from the GestãoClick /compras endpoint and use it in a supplier ranking.
Skill said: The Supabase skill requires verification after implementing a fix, but its verification guidance does not explicitly require checking whether a third-party source endpoint has status/situation dimensions whose omission changes the returned dataset.
Expected: Before declaring an imported cache complete, the workflow should compare the source's available situations/statuses with the situations represented in the cache, verify counts by situation, and avoid concluding that a small default response is the complete dataset. In this case, omitting explicit situation enumeration produced only 14 purchases from one default situation; querying all 6 situations produced 1,270 purchases (1,248 valid and 22 cancelled).
Source
File: SKILL.md
Section: Core Principles > 2. Verify your work
Fix suggestion
Expand the verification checklist for caches populated from third-party APIs. Require checking pagination, date filters, hidden/default statuses or situations, counts grouped by source status, duplicates, exclusions, and reconciliation against the source UI or an independent aggregate before describing a cache load as complete.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/agent-skills
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
supabase/agent-skills#586 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#585 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
supabase/agent-skills#583 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
supabase/agent-skills#582 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#581 ·
All issues in supabase/agent-skills
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100