Releases: AxeWP/wp-graphql-gravity-forms
v0.11.1.1 - Hotfix
This hotfix release fixes an issue with the GitHub Updater attempting to install plugin updates from the wrong release asset.
- fix: ensure results of graphql_gf_update_repo_url are always trailing-slashed.
- chore: add Composer command for generating plugin .zip
- chore: add Github Action for adding plugin .zip to release.
v0.11.1 - reCAPTCHA Settings & Submission Confirmations
This minor release adds the reCaptcha V2 type
and publicKey
to gfSettings.recaptcha
, the validated confirmation
response to form submission mutation payloads, and fixes a handful of bugs.
- feat: Add
recaptcha
settings toGFSettings
GraphQL object. - feat: Add
SubmissionConfirmation
object tosubmitGfForm
andsubmitGfDraftEntry
mutation responses. Props: @KoduVaal - fix:
isActive
should default to true for new Confirmations / Notifications. - fix: Correctly resolve the
rangeMin
andrangeMax
GraphQL fields onNumberField
. H/t @natac13 - fix: Ensure GF Action Monitor setting keys are populated.
- fix: Ensure
checkboxValues
load the Post Category choices before attempting to process. - fix: Prevent reprocessing the
imageValueInput.url
when updatingPostImage
field values. - tests: Fix broken test asserts exposed by PHPUnit v9 + WPGraphQL Test Case v2.3.
- tests: Use
gravityformscli
for installing GF plugins in test envs. - chore: Upgrade composer deps.
v0.9.2.3 - Hotfix
- fix:
rangeMax
should useGF_Number_Field::$rangeMax
when resolving.
v0.9.2.2 - Hotfix
This hotfix release fixes an issue where the rangeMin
and rangeMax
fields on NumberField
would not always return the correct float value.
- fix: correctly return float values for
rangeMin
andrangeMax
properties.
Full Changelog: v0.9.2.1...v0.9.2.2
v0.11.0 - reCAPTCHA Validation, Plugin Updates, and GF 2.6 Support
This major release adds support for server-side captcha validation, plugin updates from the WordPress backend, and new features from Gravity Forms v2.6. We've also refactored the internal file upload mechanism to better integrate with GF's form submission lifecycle, leading to more reliable (and in some cases, more performant) results.
Lastly, we fixed the GraphQL type names on some of the Product and Shipping fields, so we can hopefully add mutation support in future minor releases (and not break back-compat).
Note: The minimum version of WPGraphQL has been bumped to v1.7.0.
What's new
- 🚨 Breaking: We've added support for server-side captcha validation with reCAPTCHA. Note: If you are already using captcha fields in your form, you will need to modify your code to to pass the validation token to
fieldValues
. - 🚨 Breaking: The
button
field onGfForm
has been deprecated in favor ofform.submitButon
. Both now use the newFormSubmitButton
GraphQL type (instead of the oldFormButton
), which adds support forlayoutGridColumnSpan
,location
andwidth
properties added in GF v2.6. - We've added support for plugin updates on the WordPress backend. A warning is displayed along with the update notice when upgrading to a version with possible breaking changes (e.g. v0.X.y ).
- We've added a new
FileUploadValues
GraphQL type to theFileUploadField
which includes thebasePath
,baseUrl
, andfilename
fields in addition to the existingurl
. These fields have also been added toImageFieldValues
.
Behind the scenes
- Added the
graphql_gf_update_repo_url
filter to control the source of the Update Checker. - Reworked the logic handling file uploads to use the native GF form submission lifecycle whenever possible.
Misc
- chore!: The minimum version of WPGraphQL is now v1.7.0.
- fix!: The
ProductHiddenProductField
,ProductSingleProductField
, andShippingSingleShippingField
have been renamed toProductHiddenField
,ProductSingleField
, andShippingSingleField
, respectively, in line with other child fields. - fix: Don't hide the
CALCULATION
,HIDDENPRODUCT
,SINGLEPRODUCT
andSINGLESHIPPING
values from theFormFieldTypeEnum
. - fix: Resolve
FormQuiz
data using the unmodeledform
data instead of theFormObject
model. - dev: The
lastPageButton
field onGFForm
has been deprecated in favor ofform.pagination.lastPageButton
, where the other pagination fields live. - dev: The
values
field onFileUploadField
has been deprecated in favor offileUploadValues
. - dev: The
GFUtils::handle_file_upload()
method has been deprecated. - dev: The
graphql_gf_form_modeled_data_experimental
filter has been deprecated in favor of WPGraphQL's nativegraphql_model_prepare_fields
.
v0.10.5 - Bugfix
This minor release fixes a few bugs in the FormsConnectionResolver
. We've also added GitHub Actions for PHPStan and GraphQL schema linting.
- fix: Prevent
gfForms
queries with thelast
argument from truncating the final node. - fix: Correctly return
hasNextPage
andhasPreviousPage
values ongfForms
connections. - dev: Refactor
bin/install-test-env
into resuable functions. - chore: Update Composer dependencies.
- chore: Add GH action to save GraphQL artifact to release.
- tests: Add GH Action for GraphQL schema linting.
- tests: Add GH Action for PHPStan
v0.10.4 - Entry Counts and Quiz Results
This minor release adds a form's total entries count
and its quizResults
to the GfFormToGfEntryConnection
connection.
E.g.:
query {
gfForm(id: $id, idType: $idType) {
entries {
count # the number of entries submitted
quizResults { # The quiz results summary
averagePercentage
passRate
gradeCounts { # the frequency of each grade
count
grade
}
fieldCounts { ## the individual field breakdown
correctCount
formField {
node {
label
}
}
choiceCounts { ## the frequency of each answer
count
text
}
}
}
}
}
}
- feat: Add
count
toGfFormToGfEntryConnection
. - feat: Add
quizResults
toGfFormToGfEntryConnection
. - dev: Make original form data available via the Form model.
- chore: Update Composer deps.
- chore: Fix a few GraphQL descriptions that were missing a closing
.
.
v0.10.3 - WP Jamstack Deployments Support
This minor release adds support for WP Jamstack Deployments. We also fixed a bug where non-authenticated users could not access their own entry
on the submitGfForm
payload.
- feat: Add support for WP Jamstack Deployments.
- fix: Use
graphql_gf_can_view_entries
filter to exposesubmitGfFormMutation.entry
to non-authenticated users. (h/t @robmarshall and @IlirBajrami ) - fix: Change WPGatsby Trigger from deprecated
gform_after_duplicate_form
action togform_post_form_duplicated
. - dev: add
$resume_token
and$draft_entry arguments
tographql_gf_can_view_draft_entries
. - dev: add
$entry_id
and$entry arguments
tographql_gf_can_view_entries
. - tests: use
databaseId
instead of deprecatedformId
when testingFormQueriesTest
- chore: Add new plugin logo and banner ✨
v0.10.2 - PHP 8 Support
This minor release adds official support for PHP v8.0. We also added Gravity Forms Settings to the schema.
- feat: Add support for PHP v8.0.
- feat: Add
gfSettings
to GraphQL schema. - dev: Restore
env.dist
to the repo, and add.devcontainer
to.gitignore
. - chore: Update composer deps.
v0.10.1 - Personal Data Settings
This minor release adds support for Gravity Forms Personal Data settings and the isActive
field to FormConfirmation
objects, and fixes a couple of bugs.
- feat: Add
personalData
settings toGfForm
and relevantFormField
objects. - feat: Add field
isActive
to theFormConfirmation
object (h/t @natac13). - fix: Prevent PHP notice caused by the
PostFormatTypeEnum
enum on sites withoutpost-formats
support (h/t @noshoesplease ). - fix: Ensure
timeValues.minutes
returns the 2-digit (mm
) string. - tests: Fix tests incorrectly passing when a node index isn't explicitly set.
- dev: Update composer dependencies.
- docs: Fix missing/broken links and wording regarding custom mutation support.