Skip to content

Frontend: prevent duplicate submit requests in template and fill workflows#428

Open
Arijit429 wants to merge 2 commits intofireform-core:mainfrom
Arijit429:frontend-submit-lock-hardening
Open

Frontend: prevent duplicate submit requests in template and fill workflows#428
Arijit429 wants to merge 2 commits intofireform-core:mainfrom
Arijit429:frontend-submit-lock-hardening

Conversation

@Arijit429
Copy link
Copy Markdown

🚀 Summary

This PR improves frontend production stability by preventing duplicate submissions in both template creation and form fill workflows.


✨ What Changed

Added request lock state handling in:

frontend/app.js

New submission flags:

let isTemplateSubmitting = false;
let isFillSubmitting = false;

Applied duplicate-click prevention to:

  • handleTemplateSubmit()
  • handleFillSubmit()

💡 Why This Helps

This prevents:

  • duplicate API calls
  • accidental double-click submissions
  • repeated template creation
  • repeated form fill requests
  • frontend race-condition style issues

This significantly improves request-flow stability and overall UX.


🎯 Production Impact

This hardens the frontend for real-world usage and improves reliability under fast repeated user interactions.

@Arijit429
Copy link
Copy Markdown
Author

Hi maintainers, I wanted to share a quick update on my overall progress in line with the roadmap I outlined in my post-proposal contribution plan.

Over the past few weeks, I have been consistently working across multiple layers of the project to strengthen both functionality and production readiness.

Progress so far

  • Extraction & validation workflow

    • improved structured extraction reliability
    • worked on validation logic and review-flow related fixes
    • contributed around schema consistency and error handling in the extraction pipeline
  • Backend & API stability

    • fixed database initialization / startup flow issues
    • worked on route-level integration testing for core endpoints
    • added edge-case coverage for newly introduced upload and preview routes
    • improved regression safety for critical backend workflows
  • Testing & reliability

    • added happy-path as well as negative-path integration tests
    • covered API routes for template creation, fill workflow, upload, and preview
    • focused on improving confidence for future refactors
  • Frontend / production hardening

    • recently contributed frontend request-flow stability improvements
    • added duplicate submission prevention for template creation and form fill workflows
    • improved UX and reduced repeated request issues under fast user interactions

Overall focus

My main goal has been to steadily push the project closer to production-ready stability, covering reliability from backend services to user-facing flows.

I’m really excited to continue contributing on higher-impact production features and infrastructure improvements in the upcoming PRs. Thank you for all the guidance and for maintaining such an exciting project to work on.

@marcvergees

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