Releases: FrigadeHQ/javascript
Releases · FrigadeHQ/javascript
@frigade/react@2.10.4
Patch Changes
- 9bbb311: Fix branching forms with
visibilityCriteria: after completing a step whose form data hides the optimistically-chosen next step, the client now sendsSTARTED_STEPfor the actual current step from the refreshed state instead of the now-hidden one. Previously this caused the server'scurrentStepIdto flip back to the hidden step and the form to re-render it. Preserves theSTARTED_STEP-on-complete behavior introduced in@frigade/js@0.9.7. - Updated dependencies [9bbb311]
- @frigade/js@0.9.8
@frigade/js@0.9.8
Patch Changes
- 9bbb311: Fix branching forms with
visibilityCriteria: after completing a step whose form data hides the optimistically-chosen next step, the client now sendsSTARTED_STEPfor the actual current step from the refreshed state instead of the now-hidden one. Previously this caused the server'scurrentStepIdto flip back to the hidden step and the form to re-render it. Preserves theSTARTED_STEP-on-complete behavior introduced in@frigade/js@0.9.7.
@frigade/react@2.10.3
Patch Changes
- e5c3939: Bump @frigade/js to ^0.9.7 to include the fix for sending STARTED_STEP events when completing a step.
@frigade/js@0.9.7
Patch Changes
- 2723c81: Send STARTED_STEP event for the next step when completing/skipping a step. Previously,
complete()andskip()optimistically marked the next step as started in local state but did not send the STARTED_STEP event to the API, which caused a subsequentstart()call to no-op.
@frigade/react@2.10.2
@frigade/js@0.9.6
Patch Changes
- 2ed000b: Fix race conditions in JS SDK Flows
@frigade/react@2.10.1
Patch Changes
- d600eee: Fixes an issue related to form type select/multiple
@frigade/react@2.10.0
Minor Changes
- 11f71d9: Fixes an issue with Frigade and Vite
@frigade/react@2.9.6
@frigade/js@0.9.5
Patch Changes
- 8496a7f: Fixes an issue where navigation change events were not firing in Firefox