[frano-m]

Closes #1107

What changed

• useExportToTerraResponseURL now throws Export to Terra requires exportToTerraUrl to be set in the site config. once the manifest location and request params are available and exportToTerraUrl is not configured. Before that point it still returns undefined, so the form renders as before.
• ExportToTerra JSDoc updated to describe the throw instead of "the form stays".
• New tests/useExportToTerraResponseURL.test.ts covering the missing-config throw, the pending state, the configured URL, and missing request params.

Why

Without exportToTerraUrl, clicking "Request Link" fired the analytics event and the manifest request succeeded, but the user never left the form and nothing reported the misconfiguration. The error now reaches the nearest React error boundary, so the problem is visible.

Assumptions I made

• Throw after the manifest returns, not on render. An app that renders the export view without Terra configured still loads; it only fails when a user requests the link. Side effect: the export-requested analytics event still fires before the error.
• Error boundary only. No inline error UI; the nearest React error boundary handles it.
• Scope limited to the export link step. AcceptTerraTOS and CreateTerraAccount still silently no-op on "Go to Terra" when exportToTerraUrl is unset.
• Shipped as fix:, not a breaking change. Apps that configure exportToTerraUrl are unaffected. Apps that render export to Terra without exportToTerraUrl will now see their error boundary after "Request Link" instead of a silently stuck form — set exportToTerraUrl in the site config if you use export to Terra.

How to verify

In a consuming app (e.g. data-browser) linked with scripts/link.sh:

1. With exportToTerraUrl set in the site config, go to the export to Terra page, choose a format, and click "Request Link". You should get the Terra link view as before.
2. Remove exportToTerraUrl from the site config and restart. The export to Terra form should still render. Click "Request Link": once the manifest returns, the app's error boundary should show, and the console should log Export to Terra requires exportToTerraUrl to be set in the site config.
3. Run npm test -- tests/useExportToTerraResponseURL.test.ts in findable-ui; all four tests pass.

Definition of done:

• With no exportToTerraUrl configured, the export to Terra flow throws an error with a message naming the missing config. → step 2
• With exportToTerraUrl configured, export to Terra behaves as before. → step 1
• A test covers the missing-config case. → step 3

🤖 Generated with Claude Code
🐦 Built with cc-claude-tools

[Copilot]

🟢 Approval recommended

The focused change preserves existing configured behavior and has regression coverage; no blockers were found, though tests were not executed.

No open issues 🎉

What changed in this PR

Addresses #1107 by surfacing missing Terra export configuration instead of silently leaving users on the form.

Changes:

• Throws a descriptive error once the manifest location and request parameters are available.
• Preserves pending and configured behavior.
• Updates documentation and adds four focused tests.

File	Description
tests/​useExportToTerraResponseURL.test.ts	Tests missing configuration, pending states, and configured exports.
src/​hooks/​useExportToTerraResponseURL.ts	Throws when a completed request lacks Terra configuration.
src/​components/​Export/​components/​ExportToTerra/​exportToTerra.tsx	Updates JSDoc to describe the error behavior.

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The narrowly scoped change satisfies the issue requirements with no identified blocking issues; tests were inspected but not executed.

No open issues 🎉

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The focused guard change meets the issue requirements, preserves configured exports, and has regression coverage; tests were not executed during this review.

No open issues 🎉

_{Review effort: Balanced}

[NoopDog]

Thanks Fran, this is cleanly done. But every app that uses export to Terra sets exportToTerraUrl, so nothing can reach this case today. Let's not add code and tests for it. I'll close this and #1107 as not planned.