r2mo-ui-upload

Frontend image upload with preview and validation is handled by binding schema attributes like accept, max_size, and preview to a form field. This generates upload controls that enforce size and format rules while displaying live image previews.

File upload limits like max_count and max_size are enforced automatically by deriving controls from parsed front-matter attributes. The upload component reads these constraints directly from the schema, eliminating the need to hardcode validation logic.

Spec-driven file upload aligns with backend API contracts by using api_refs to deduce the endpoint, field names, and response mapping. This ensures the frontend upload component submits data to the correct backend path without hardcoded integration assumptions.

Image cropping during file upload is triggered when the crop attribute is present in the schema. The upload component adapts to list or form contexts, applying cropping functionality alongside preview and progress indicators.

This frontend upload component works for both pageform and pagelist contexts. It adapts its upload controls to the bound schema, allowing file and image uploads to function seamlessly whether placed in a form field or a list cell.

Upload API endpoints are configured without hardcoding paths by referencing api_refs from the spec. The component deduces the API contract, including the endpoint and response mapping, directly from these specification references.