feat(catalog): enable logo file upload in theme editor

[drernie]

Summary

• Implements useUploadFile in CatalogSettings.tsx to upload the logo image to the service bucket at catalog/logo.<ext> and return an s3:// URL
• Removes the useThirdPartyDomainForLogo flag in ThemeEditor.tsx so the drag-and-drop file input is shown instead of the URL text field
• The Logo component already supports s3:// URLs (signs them via AWS credentials before rendering), so no further changes are needed

Test plan

• In Admin > Settings > Theme, click "Configure theme" — verify a drag-and-drop zone appears instead of a URL text field
• Drop a PNG/JPG logo image — verify it uploads to s3://<service-bucket>/catalog/logo.<ext> and the logo appears in the navbar
• Verify that removing the theme also clears the logo
• All existing Logo unit tests pass (vitest run "Logo")

🤖 Generated with Claude Code

Greptile Summary

This PR activates logo file upload in the theme editor by implementing useUploadFile in CatalogSettings.tsx (uploading to catalog/logo.<ext> in the service S3 bucket) and flipping useThirdPartyDomainForLogo to false in ThemeEditor.tsx so the drag-and-drop InputFile component is shown instead of the URL text field.

Key points:

• The useUploadFile implementation is clean and correct — reads the file buffer, infers the extension from the filename, uploads via s3.putObject, and returns an s3:// URL that the existing Logo component can sign and render.
• Enabling InputFile exposes a pre-existing URL.createObjectURL memory leak in that component: blob URLs are created on every file drop but URL.revokeObjectURL is never called — neither on value change nor on unmount. This code path was unreachable before this PR.
• The dropzone has no accept constraint, allowing non-image files to be uploaded to S3 as a logo.
• useThirdPartyDomainForLogo is now a dead constant (false); the ternary branch for true in the render is unreachable and can be removed.

Confidence Score: 4/5

• Safe to merge after fixing the ObjectURL memory leak; the remaining issues are non-blocking style/best-practice cleanups.
• The core upload logic is correct and well-scoped. The memory leak in InputFile is a real bug activated by this PR (P1) but it only affects the admin settings dialog — a low-traffic, admin-only surface — so it won't cause production reliability problems in normal usage. The missing accept restriction and the dead code are P2 cleanups.
• catalog/app/containers/Admin/Settings/ThemeEditor.tsx — the InputFile component's URL.createObjectURL call needs a corresponding revokeObjectURL cleanup.

Important Files Changed

Filename	Overview
catalog/app/utils/CatalogSettings.tsx	Implements useUploadFile — uploads a file to catalog/logo.<ext> in the service S3 bucket and returns an s3:// URL. Implementation is straightforward; minor note that old logo files at different extensions (e.g. logo.png vs logo.jpg) are never cleaned up on overwrite.
catalog/app/containers/Admin/Settings/ThemeEditor.tsx	Flips useThirdPartyDomainForLogo to false, activating the InputFile dropzone branch. This exposes a pre-existing URL.createObjectURL memory leak (no revokeObjectURL cleanup) and a missing accept constraint on the dropzone. The flag variable itself becomes dead code.

Sequence Diagram

sequenceDiagram
    actor User
    participant InputFile
    participant ThemeEditor
    participant useUploadFile
    participant S3

    User->>InputFile: Drop image file
    InputFile->>ThemeEditor: onChange(File)
    User->>ThemeEditor: Click Save
    ThemeEditor->>useUploadFile: uploadFile(File)
    useUploadFile->>S3: putObject to catalog/logo.ext
    S3-->>useUploadFile: success
    useUploadFile-->>ThemeEditor: object URL returned
    ThemeEditor->>S3: writeSettings with updated logo
    S3-->>ThemeEditor: success
    ThemeEditor->>ThemeEditor: close dialog

Loading

Comments Outside Diff (2)

1. catalog/app/containers/Admin/Settings/ThemeEditor.tsx, line 132-135 (link)

   ObjectURL memory leak — revocation missing

   URL.createObjectURL creates a persistent blob URL that is never released. Every time the user drops a new file, the old blob URL is abandoned in memory and never cleaned up. When the dialog closes and the component unmounts, the same happens. This branch was dead code before this PR (guarded by the now-removed useThirdPartyDomainForLogo = true flag), so this leak is effectively introduced here.

   A useEffect with cleanup should replace the useMemo:

2. catalog/app/containers/Admin/Settings/ThemeEditor.tsx, line 128-131 (link)

   Dropzone accepts all file types

   The dropzone has no accept constraint, so users can drop arbitrary files (PDFs, videos, executables, etc.) as a logo. These will be uploaded to S3 and saved as the logo URL. Adding an accept list restricts both the native file picker and the drop validation:

_{Reviews (1): Last reviewed commit: "feat(catalog): enable logo file upload i..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review.

_{Tip: disable this comment in your organization's Code Review settings.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.05%. Comparing base (b6048c8) to head (74ae447).

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #4781       +/-   ##
===========================================
+ Coverage   45.62%   94.05%   +48.42%     
===========================================
  Files         831      146      -685     
  Lines       33597    11766    -21831     
  Branches     5727        0     -5727     
===========================================
- Hits        15328    11066     -4262     
+ Misses      16264      700    -15564     
+ Partials     2005        0     -2005     

Flag	Coverage Δ
api-python	93.14% <ø> (ø)
catalog	?
lambda	96.63% <ø> (ø)
py-shared	98.18% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[drernie]

Test results against quilt-staging (us-east-1)

All 9/9 checks passed after running the E2E test suite with a headed Playwright browser against the live nightly stack.

Results

Check	Result
Catalog loads authenticated	✅
Admin Settings page loads with Theme section	✅
Drop-zone InputFile rendered (not URL text field)	✅
URL text field absent	✅
Logo preview visible after file selection	✅
Dialog closed after Save	✅
S3 PUT to catalog/logo.* captured	✅
Logo image visible in navbar	✅
settings.json persisted with s3://…/catalog/logo.png	✅

Infrastructure change required

The catalog-config inline policy on the ReadWriteQuiltV2 IAM role only allowed s3:PutObject on catalog/settings.json. The logo upload writes to catalog/logo.<ext>, which was blocked (403). The policy needs one additional statement in the stack template that provisions this role:

{
  "Action": "s3:PutObject",
  "Resource": "arn:aws:s3:::${ServiceBucket}/catalog/logo.*",
  "Effect": "Allow"
}

Applied to staging manually for testing; needs to be added to the stack CDK/CFN definition before deploying to other stacks.