Skip to content

fix: FollowupPanel input submission bug #516

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ngoiyaeric merged 1 commit into from
Feb 13, 2026
Merged

fix: FollowupPanel input submission bug #516

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions components/followup-panel.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ import type { AI } from '@/app/actions'
import { UserMessage } from './user-message'
import { ArrowRight } from 'lucide-react'
import { useMapData } from './map/map-data-context'
import { nanoid } from '@/lib/utils'

export function FollowupPanel() {
const [input, setInput] = useState('')
Expand All @@ -17,10 +18,11 @@ export function FollowupPanel() {

const handleSubmit = async (event: React.FormEvent<HTMLFormElement>) => {
event.preventDefault()
const formData = new FormData(event.currentTarget as HTMLFormElement)
const formData = new FormData()
formData.append("input", input)

const userMessage = {
id: Date.now(),
id: nanoid(),
isGenerating: false,
component: <UserMessage content={input} />
}
Comment on lines 19 to 28

@charliecreates charliecreates Bot Feb 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Manual FormData construction fixes the controlled-input issue, but this handler currently trusts input as-is. If the user submits whitespace, you’ll append an empty/meaningless message and still call submit, which can create confusing UX and unnecessary server work. Consider trimming and early-returning (or disabling submit) when empty.

Suggestion

Trim and guard against empty submissions before building messages / calling submit:

const handleSubmit = async (event: React.FormEvent<HTMLFormElement>) => {
  event.preventDefault()

  const value = input.trim()
  if (!value) return

  const formData = new FormData()
  formData.append('input', value)

  const userMessage = {
    id: nanoid(),
    isGenerating: false,
    component: <UserMessage content={value} />
  }
  // ...
}

Reply with "@CharlieHelps yes please" if you'd like me to add a commit with this suggestion.

Expand Down