Fix submission button stuck in initial state during API call

[Copilot]

The submit button never transitioned to a processing state, leaving users uncertain if their submission was accepted. Multiple clicks could trigger duplicate API calls.

Changes

• Added isSubmitting state to track submission lifecycle
• Updated submitApplication function:
  • Guard against duplicate submissions with early return
  • Set button to processing state before API call
  • Added try-catch to handle network errors
  • Reset state on failure to allow retry
• Updated button disabled logic to include isSubmitting check

async function submitApplication() {
  if (isSubmitting) return
  
  setIsSubmitting(true)
  setSubmitButton(`⏳ ${returnLocalizedMessage(router.locale, 'PROCESSING')}`)
  
  try {
    const submissionAPICall = await fetch(/*...*/)
    // Handle success/error and reset state on failure
  } catch (error) {
    setSubmitButton(`❌ ${returnLocalizedMessage(router.locale, 'ERROR')}`)
    setIsSubmitting(false)
  }
}

Button now properly transitions: Initial → Processing → Success/Error

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
apply	Ready	Preview	Comment	Nov 1, 2025 10:09pm

[leowilkin]

📝 Changed routes:

…ation]/[leader]/review
(view full size)

Commit 6fb97f5 (https://apply-44vko4gf8.hackclub.dev).

[alf1e]

bad AI, didnt fix