Fix answer missing type error

[Kyle9410-Chen]

Type of changes

• Fix

Purpose

• Fix answer missing type error

[Copilot]

Pull request overview

This PR addresses a “missing answer type” error by preventing auto-save from including answers for questions that are not present in the currently visible sections (and therefore not present in the derived questionTypeMap).

Changes:

• Filter answers during auto-save payload construction to only include answers whose questionId exists in the current sections.
• Avoid generating update payload entries with an undefined questionType (root cause of the error).

Comments suppressed due to low confidence (1)

src/features/form/components/FormDetailPage.tsx:284

• answersArray now scans sections for each answer (sections.some(...some...)) even though questionTypeMap is already built from the same sections. You can avoid the extra nested traversal (and make the intent clearer) by filtering on the presence of questionTypeMap[questionId] (or building a Set of valid questionIds once) instead of re-walking sections per entry.

			.filter(([questionId]) => sections.some(section => section.questions?.some(q => q.id === questionId)))
			.filter(([questionId, value]) => value !== "" && !["UPLOAD_FILE", "OAUTH_CONNECT"].includes(questionTypeMap[questionId]))

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This new filter prevents sending answers whose questionType is missing from questionTypeMap (e.g., when a section becomes hidden). However, the submit path (handleSubmit builds answersArray separately later in this file) still constructs payloads from all answers without filtering out questionIds that aren’t in sections/questionTypeMap, so the same “missing type” error can still occur on submit. Consider extracting a shared helper to build the answers payload and reuse it in both auto-save and submit, or apply the same filtering logic in handleSubmit.