Skip to content

Conversation

@ephraimduncan
Copy link
Contributor

Summary

  • Change hasReturningUrl from protectedProcedure to publicProcedure
  • Form completion pages (/s/[formId]) were causing sporadic UNAUTHORIZED errors for anonymous form submitters
  • The returnUrl is not sensitive data and formId is already exposed in the URL

Test plan

  • Build succeeds (bun run build)
  • Unauthenticated access to /s/[any-form-id] no longer returns 500
  • Authenticated users still see correct returnUrl behavior

Form completion pages (/s/[formId]) need to check if a returnUrl exists,
but were using protectedProcedure which caused sporadic UNAUTHORIZED
errors for anonymous form submitters.
- "has" prefix implies boolean but returns actual URL value
- Aligns with codebase convention for data fetching procedures
@ephraimduncan ephraimduncan merged commit d7a80e3 into main Jan 26, 2026
3 of 4 checks passed
@ephraimduncan ephraimduncan deleted the fix/public-has-returning-url branch January 26, 2026 11:13
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