fix: pass useUpload hook at F0Form level instead of field-level

[sauldom102]

Move useUpload from file field config to F0Form level

What

Lifts the useUpload hook from individual file field configurations (f0FormField) to a form-level prop on <F0Form>. All file fields in a form now share the same upload hook provided once at the form level.

Why

Previously, every file field required its own useUpload in the field config, leading to repetitive boilerplate. Since all file fields in a form typically use the same upload mechanism, it makes more sense to declare it once at the form level.

Changes

• fields/file/types.ts — Removed useUpload from F0FileConfig and F0FileField
• types.ts — Added useUpload?: UseFileUpload to all 4 form prop interfaces (F0FormPropsWithSingleSchema, F0FormPropsWithPerSectionSchema, F0FormPropsWithSingleSchemaDefinition, F0FormPropsWithPerSectionDefinition)
• context.ts — Added useUpload to F0FormContextValue so file fields can access it via context
• F0Form.tsx — Threads useUpload through all code paths (single schema, per-section, definition adapters) into the form context
• F0FormSection.tsx — Accepts and forwards useUpload into section-level context
• FileFieldRenderer.tsx — Resolves useUpload from context instead of field.useUpload
• f0Schema.ts — Removed useUpload-based file field type inference (file fields must use fieldType: "file" explicitly)
• useSchemaDefinition.ts — Removed useUpload mapping in the file field case
• Stories & tests — Updated to pass useUpload at the <F0Form> level

Usage

// Before
f0FormField(z.string(), {
  fieldType: "file",
  useUpload: useMyUpload,
})

// After
f0FormField(z.string(), { fieldType: "file" })

<F0Form
  formDefinition={formDefinition}
  useUpload={useMyUpload}
/>

[github-actions]

✅ No New Circular Dependencies

No new circular dependencies detected. Current count: 0

[github-actions]

📦 Alpha Package Version Published

Use pnpm i github:factorialco/f0#npm/alpha-pr-3752 to install the package

Use pnpm i github:factorialco/f0#f930612c3eedc444dc8ac21d3e63136391e04ffe to install this specific commit

[github-actions]

🔍 Visual review for your branch is published 🔍

Here are the links to:

• the Visual Review Page

• the latest build on chromatic

• the full storybook

[Copilot]

Pull request overview

This PR refactors F0Form’s file upload configuration by moving useUpload from per-field config to a single, form-level prop that is exposed to file fields through F0FormContext.

Changes:

• Adds useUpload?: UseFileUpload to F0Form props and threads it into F0FormContext (single schema, per-section, and definition adapters).
• Removes useUpload from file field config/runtime field types and removes useUpload-based file type inference.
• Updates file field rendering/tests/stories to source upload behavior from the form-level useUpload.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
packages/react/src/components/F0Form/useSchemaDefinition.ts	Stops mapping useUpload from schema definition config into runtime fields.
packages/react/src/components/F0Form/types.ts	Adds useUpload?: UseFileUpload to all F0Form prop interfaces.
packages/react/src/components/F0Form/fields/file/types.ts	Removes useUpload from F0FileConfig/F0FileField types.
packages/react/src/components/F0Form/fields/file/tests/FileFieldRenderer.test.tsx	Removes some field-level useUpload usage (but still needs further updates).
packages/react/src/components/F0Form/fields/file/FileFieldRenderer.tsx	Switches upload hook resolution from field.useUpload to context?.useUpload.
packages/react/src/components/F0Form/f0Schema.ts	Removes inferring fieldType: "file" based on useUpload.
packages/react/src/components/F0Form/context.ts	Adds useUpload?: UseFileUpload to F0FormContextValue.
packages/react/src/components/F0Form/components/F0FormSection.tsx	Accepts/forwards useUpload into section-level context provider value.
packages/react/src/components/F0Form/stories/F0Form.stories.tsx	Updates file-field stories to pass useUpload at the <F0Form> level.
packages/react/src/components/F0Form/F0Form.tsx	Threads useUpload through all <F0Form> render paths into context.

Comments suppressed due to low confidence (1)

packages/react/src/components/F0Form/fields/file/tests/FileFieldRenderer.test.tsx:94

• This test suite still has upload scenarios that don't provide a form-level useUpload prop, so selecting a file will never trigger an upload (and assertions like expecting signed_*.pdf will fail). Also, there is still at least one remaining useUpload usage inside a f0FormField config later in this file, which no longer matches the new API/type. Update these tests to pass useUpload={createMockUploadHook(...)} to <F0Form> and remove any remaining field-level useUpload config usage.

describe("FileFieldRenderer", () => {
  it("renders a dropzone with default text", () => {
    const schema = z.object({
      file: f0FormField(z.string().optional(), {
        label: "Document",
        fieldType: "file",
      }),
    })

    render(
      <F0Form
        name="test-file"
        schema={schema}
        defaultValues={{ file: "" }}
        onSubmit={async () => ({ success: true })}
      />
    )

[Copilot]

useUpload was removed from F0FileField, which makes standalone file fields (e.g. F0FormField where there is no F0FormContext.Provider) unable to upload at all. With the current FileFieldRenderer implementation relying on context, consumers have no way to supply an upload hook for standalone rendering. Consider either keeping useUpload on the runtime F0FileField for non-form usage, or adding a useUpload prop to F0FormField (and/or a way to inject it into context) so file uploads still work outside <F0Form>.

Suggested change

	description?: string
	description?: string
	/**
	* Consumer-provided upload hook.
	*
	* This is primarily used for standalone file fields rendered outside of
	* `<F0Form>` / `F0FormContext.Provider`, where the upload hook cannot be
	* supplied via context.
	*/
	useUpload?: UseFileUpload

[Copilot]

File uploads are now sourced from context?.useUpload, but when useUpload isn't provided the UI still lets users pick/drop files and then uploads never start (because FileUploadItem no-ops without an upload hook). Please add an explicit guard (e.g. hide/disable the dropzone when no useUpload is configured, or surface a clear error/throw when a new file is added) so misconfiguration doesn't fail silently.