Skip to content

fix(firefox): Don't error when an addon has no description or summary - #13

Open
shadoath wants to merge 1 commit into
wxt-dev:mainfrom
whiteboard-works:fix/firefox-null-description
Open

shadoath wants to merge 1 commit into
wxt-dev:mainfrom
whiteboard-works:fix/firefox-null-description

Conversation

@shadoath

Copy link
Copy Markdown
Contributor

Summary

  • AMO returns null instead of a locale map when a listing leaves the description or summary empty. Object.values(null) threw, so the resolver returned null for the whole addon and it disappeared from the wxt.dev showcase (it hit 2 of the 73 showcase Firefox slugs, and TabWatch before its listing got a description).
  • Localized fields now fall back to "", which keeps longDescription/shortDescription valid for the non-null GraphQL schema. Added firefox-api.test.ts covering both the normal and null cases.
  • How this could fail: another AMO field (e.g. ratings, current_version) can also be null and still nulls the addon; that's no worse than today and is outside this fix.

chrome-crawler.e2e.test.ts fails locally on main as well (it crawls the live Chrome Web Store), so it's unrelated to this change.

🤖 Generated with Claude Code

https://claude.ai/code/session_015ePekSUNprhYv49RLVbznD

AMO returns `null` instead of a locale map when a listing leaves the description or summary empty, so `Object.values` threw and the whole addon resolved to `null` in GraphQL.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015ePekSUNprhYv49RLVbznD
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant