Skip to content

Releases: EvanSchleret/FormForgeClient

v1.1.0

14 Apr 22:45
ab6f147

Choose a tag to compare

FormForge Client v1.1.0 🚀

I'm excited to announce v1.1.0, focused on stronger standalone integration, clearer publishing workflows, and better validation control in embedded/custom form setups.

This release improves how FormForge works when integrated into external parent forms while also simplifying management API publication behavior through payload-driven actions.

✨ Highlights

  • Payload-driven auto-publication for form create/update workflows
  • defaultPublished builder behavior aligned with create/patch actions (no extra publish call)
  • Better standalone validation ergonomics with exposed renderer validation APIs
  • Improved blur-based validation behavior in external v-model integrations
  • Continued stability improvements for scoped route resolution

➕ Added

  • Management payload support for:
    • auto_publish: true
    • autoPublish: true (normalized to auto_publish)
  • FormForgeRenderer exposed methods for host apps:
    • validate(options?)
    • validateField(name)
    • clearErrors(path?)
    • getErrors(path?)
  • New renderer props for validation triggers:
    • validateOn
    • validateOnBlur

⚡ Improved

  • Builder save flow now supports auto-publication via payload on create/patch
  • defaultPublished now relies on the management mutation path instead of issuing a separate /publish request
  • Standalone/external-model UX with explicit field-level blur validation handling
  • Scope param resilience when resolving named scoped routes after navigation

🐛 Fixed

  • Cases where named scope params could be missed after route transitions
  • TypeScript lint issue (no-explicit-any) in submission response typing

** 📘 Full Changelog**: v1.0.0...v1.1.0

v1.0.0

08 Apr 11:33
735ed52

Choose a tag to compare

FormForge Client v1.0.0

I'm excited to announce v1.0.0, the first stable release of FormForge Client.

This release marks the transition from iterative development to a production-ready baseline, with a strong focus on reliability, developer ergonomics, and a consistent end-user experience across the client package and the Laravel backend package.

Highlights

  • Stable, versioned API and client behavior for core form workflows
  • Improved SSR-friendly data loading and rendering consistency
  • Stronger validation and error handling across critical flows
  • Better type safety and maintainability in frontend and backend code
  • Expanded automated test coverage and CI confidence for release quality

Added

  • Initial stable feature set for form creation, editing, and submission workflows
  • Structured request validation and standardized JSON API responses
  • Reusable frontend composables for shared app logic
  • Improved SEO metadata handling for public-facing pages

Improved

  • Performance across key rendering and data-fetching paths
  • DX for local development, linting, and type-checking workflows
  • Internal architecture with clearer separation between controllers and business logic

Fixed

  • Inconsistent handling of edge-case validation errors
  • SSR/CSR mismatch issues in selected views
  • Multiple stability issues discovered during pre-1.0 hardening

Full Changelog: v1.0.0 establishes the stable foundation for the 1.x line, with future releases focused on incremental features, performance, and ecosystem integrations.