Releases: AxeWP/wp-graphql-gravity-forms
v0.11.11 - Bugfix
This minor release fixes a bug where the provided IP address was not saved correctly when using the submitGfForm
mutation.
What's Changed
- fix: Properly store provided IP when submitting an entry. Thanks @marcusforsberg !
- chore: Update composer deps.
Full Changelog: v0.11.10...v0.11.11
v0.11.10 - Gravity Forms v2.6.8+ Compatibility
This minor release adds compatibility for Gravity Forms v2.6.8+ by refactoring the internal logic used for uploading files to use native Gravity Forms methods whenever possible.
- fix: Refactor File Upload logic for compatibility with Gravity Forms 2.6.8+.
- chore: Update composer deps.
Full Changelog: v0.11.9...v0.11.10
v0.11.9 - WPGraphQL v1.13.x Compatibility
This minor release adds compatibility for WPGraphQL v1.13.x, by removing the new Connection
, Edge
, and OneToOneConnection
GraphQL interfaces from the FormField
connections. This is a temporary fix, and will be reverted in a future release.
- fix: remove incompatible interfaces from
FormField
connections. - fix: remove redundant
There was an error while processing the form.
prologue from submissionUserError
s. - chore: update Composer deps.
- chore: fix PHPStan issues surfaced by new Composer deps.
Full Changelog: v0.11.8...v0.11.9
v0.11.8 - Bugfix
This minor release fixes an issue where querying for NumberField.calculationRounding
would sometimes throw an error when Rounding
is set to Do not round
.
- fix: explicitly set
calculationRounding
tonull
when rounding is disabled. - chore: update Composer deps.
Full Changelog: v0.11.7...v0.11.8
v0.11.7 - Bugfix
This minor release fixes an issue with the GraphQL dataloader storing the GF form, instead of the 'prerendered' version used by many 3rd-party plugins. It also fixes FormQuiz
GraphQL fields from resolving if they are not associated with the current gradingType
(e.g. passPercent
on a LETTER
grade ).
- fix: Run
gform_pre_render
on Form objects before they are stored in the DataLoader. - fix: FormQuiz fields should return null is not associated with current
gradingType
. - chore: Update Composer deps.
Full Changelog: v0.11.6...v0.11.7
v0.11.6 - Bugfix
This minor release fixes a bug where the resolver for FormField.choices
wasn't always correctly parsing and passing the data, causing GraphQL fields on Quiz and Chained Select choices to return incorrect values.
- fix:
FormField.choices
doesn't always resolve values correctly. - chore: replace abandoned
poolshark/wp-graphql-stubs
Composer dependency withaxewp/wp-graphql-stubs
.
v0.11.5 - Quiz Setting Bugfixes
This minor release fixes a bug where gfForm.quiz
data was not resolving, as well as changes the GraphQL types for FormQuizConfirmation
fields.
Note: This release is technically a breaking schema change, however since those fields are entirely unusable with their current type definitions, we don't expect this have any negative impact on users when upgrading.
- (#314) fix!: Change GraphQL field
FormQuizConfirmation.isAutoformatted
from typeString
to typeBoolean
. - (#314) fix!: Change GraphQL field
FormQuizConfirmation.message
from typeInt
to typeString
. - (#314) fix: Fix resolver for
GfForm.quiz
returning empty data. - (#314) test: Add basic WPUnit tests for
GfForm.quiz
data. - (#315) test: Fix
FormConnectionQueriesTest
classname corrupted after backporting from v0.11.4.
Full Changelog: v0.11.4...v0.11.5
v0.11.4
This minor release fixes a bug where form.entries
would return entries from all forms, among other things.
- (#291) feat: Update
plugin-update-checker
tov4.13
and enable use of local assets on Dashboard screen. - (#307) fix: ensure form->entry connections only return entries on that form.
- (#307) fix: change
formIds
input description to clarify that it (currently) only accepts database IDs. - (#304) chore: update Composer deps.
- (#307) test: ensure
$_gf_state
is reset between tests. - (#307) test: add some extra WPUnit tests for form/entry connection where args.
Full Changelog: v0.11.3...v0.11.4
v0.11.3 - WPGraphQL v1.9.0 Compatibility
This minor release fixes a bug where gfEntries.pageInfo
fields would have incorrect data after upgrading to WPGraphQL v1.9.0.
Note: As a result of WPGraphQL v1.9.0, the order of items returned when using backwards pagination (e.g. last:5
) is now reversed and identical to the order of items returned when using forward pagination, as per the GraphQL Relay spec.
- fix: Refactor
EntriesConnectionResolver
to support WPGraphQL v1.9.0. - test: refactor
gfForms
andgfEntries
pagination tests.
Full Changelog: v0.11.2...v0.11.3
v0.11.2 - Build Scripts, Confirmations, & DataLoaders
This minor release fixes a bug where querying for a non-existent Form/Entry ID would throw an error instead of returning null
.
We also added some new GraphQL fields and connections to the FormConfirmation
and SubmissionConfirmation
types, and made some under-the-hood improvements to both the code and our build scripts.
- feat: Add
isAutoformatted
to theFormConfirmation
object. - feat: Add
Page
connection to theFormConfirmation
object. (h/t @robmarshall ) - feat: Add
pageId
andqueryString
fields andPage
connection to theSubmissionConfirmation
object. - fix: Ensure DataLoader keys return null on non-existent objects, instead of throwing errors. (h/t 6x x6 and Jonathan Ng )
- dev: Fix return type for
Utils::get_possible_form_field_child_types()
. - dev: Refactor ignored Gravity Forms settings to
FormFields::ignored_gf_settings()
. - dev: Ensure composer deps are built for PHP 7.4.
- chore: Update Composer deps.
- docs: Add usage example for file uploads.
- ci: Various improvements to workflows.
Full Changelog: v0.11.1.1...v0.11.2