GraphQL API for interacting with Gravity Forms.
This patch release fixes the version number in the plugin header, which was incorrectly set to 0.12.5 instead of 0.12.6.
Full Changelog: https://github.com/AxeWP/wp-graphql-gravity-forms/compare/v0.12.6...0.12.6.1
This minor release adds explicit support for PHP 8.2 and WordPress 6.5 - including the new Plugin Dependency header. Additionally, we've updated the Composer dependencies, and improved code quality and type safety.
Full Changelog: https://github.com/AxeWP/wp-graphql-gravity-forms/compare/v0.12.5...v0.12.6
This minor release fixes a bug where EmailField.inputs were returning null when Email Confirmation is disabled and an issue where formFields were not being correctly filtered by their where args.
We've also updated the Composer dependencies, did some code linting, and tested compatibility against WordPress 6.4.x.
EmailField inputs are hydrated when Email Confirmation is disabled. H/t @gytjarek.yahnis-elsts/plugin-update-checker to v5.3.axepress/wp-graphql-cs to v2.0.0-beta.2 and fix resulting issues.Full Changelog: https://github.com/AxeWP/wp-graphql-gravity-forms/compare/v0.12.4...v0.12.5
This minor release fixes a bug where updating the plugin via the WordPress backend would fail due to changes to GitHub's API.
Note: Users relying on WordPress's built-in plugin update mechanism will need to update manually to this version by downloading the release zip.
yahnis-elsts/plugin-update-checker to v5.2.Full Changelog: https://github.com/AxeWP/wp-graphql-gravity-forms/compare/v0.12.3...v0.12.4
This minor release fixes a few bugs when resolving GfEntry data, and addresses some code smells from the updated WPGraphQL Coding Standards. We're also now testing the plugin against WordPress 6.3 and PHP 8.1.
count.QuizResults data.QuizResults resolver.WPLoader.loadOnly to true for acceptance suite. Thanks @lucatume!Full Changelog: https://github.com/AxeWP/wp-graphql-gravity-forms/compare/v0.12.2...v0.12.3
This minor release expands the ability to use database and global IDs interchangeably in more connections. We also now prime the GFFormsLoader dataloader, reducing the number of database queries and improving performance.
We've also implemented the new WPGraphQL Coding Standards ruleset for PHP_CodeSniffer. While many of the (over 1000+) addressed sniffs are cosmetic, numerous smells regarding performance, type safety, sanitization, and 3rd-party interoperability have been fixed as well.
ID type is indeterminate. Note: The following input args now work with both database and global IDs: GfEntriesConnectionWhereArgs.formIds, GfFormsConnectionwhereArgs.formIds.WPGraphQL\Data\DataSource::resolve_post_object() method.axepress/wp-graphql-cs PHP_Codesniffer ruleset, and fix all resulting issues.productValues input when submitting forms.Full Changelog: https://github.com/harness-software/wp-graphql-gravity-forms/compare/v0.12.1...v0.12.2
This minor release fixes an issue where certain complex Field Input and Field Choice types would try to implement a non-existent parent interface, causing GraphQL debug messages to be returned in the response.
FieldInputRegistry and FieldChoiceRegistry to prevent the registration of duplicate/nonexistent types.extensions['debug'] messages are returned when querying FormFields.graphql-schema-linter error for FormFieldConnection.pageInfo missing a description. This will be reverted once FormFieldConnection is refactored to be a Relay-compatible.Full Changelog: https://github.com/harness-software/wp-graphql-gravity-forms/compare/v0.12.0...v0.12.1
:warning: This release contains multiple breaking changes.
This major release refactors the way Gravity Forms fields are registered in GraphQL, by using GraphQL interfaces derived from the Forms Field Settings to register the fields, choices, and inputs tp the type. This allows for more flexibility in how fields are registered and consumed, and for DRYer GraphQL queries and frontend components.
This release also adds explicit support for Pricing Fields. Specifically, we've added support for the Option, Product, Quantity, Shipping, and Total fields, and the orderSummary field on GfEntry.
Lastly, we've exposed the connectedChoice and connectedInput fields on CheckboxFieldValue objects, added some additional test coverage, and squashed a few bugs along the way.
Note: The minimum version of WPGraphQL has been bumped to v1.9.0.
formField.choices and formField.inputs to use the new FormFieldChoice and FormFieldInput interfaces, respectively.Option, Product, Quantity, Shipping, and Total Gravity Forms fields.orderSummary field to GfEntry objects, which contains all the order details for the form submission.connectedChoice and connectedInput fields to CheckboxFieldValue objects, to make it easier to access specific values of the selected choices and inputs without hacky workarounds.FormField.id field in favor of FormField.databaseId, which is more consistent with WPGraphQL's naming conventions. Note: FormField.id will change its type to a global (Relay) ID in an upcoming release.AddressField.defaultProvince changed type from String to AddressFieldProvinceEnum.AddressField.defaultState changed type from String to AddressFieldProvinceEnum.{FieldType}.inputs fields changed type from [AddressInputProperty] to [GfFieldInput].{FieldType}.choices changed type from [ChainedSelectFieldChoice] to [GfFieldChoice].SUBMIT was removed from enum FormFieldTypeEnum.PostCategoryFieldChoice kind changed from ObjectTypeDefinition to InterfaceTypeDefinition.PostCategoryInputProperty was removed.PostCustomInputProperty was removed.PostTagsInputProperty was removed.QuizFieldChoice kind changed from ObjectTypeDefinition to InterfaceTypeDefinition.QuizInputProperty was removed.SubmitField was removed.personalData when resolving the form model.FormsConnectionOrderbyInput.field in favor of FormsConnectionOrderbyInput.column
TypeRegistry classes to WPGraphQL\GF\Registry namespace.add_action() call.$type_registry param from Registrable::register() interface method.$type_registry param from the graphql_gf_after_register_types and graphql_gf_before_register_types actions.PropertyMapper, ChoiceMapper, InputMapper, and FieldProperties PHP classes in favor of the FormFieldRegistry, FieldInputRegistry and FieldChoiceRegistry classes.graphql_gf_after_register_form_field, graphql_gf_after_register_form_field_object.graphql_gf_form_field_settings_with_inputs
graphql_gf_form_field_settings_with_choices
graphql_gf_form_field_setting_choice_fields, graphql_gf_form_field_setting_input_fields, graphql_gf_registered_form_field_setting_classes, graphql_gf_registered_form_field_setting_choice_classes, graphql_gf_registered_form_field_setting_input_classes.graphql_gf_form_field_setting_properties filter in favor of graphql_gf_form_field_setting_fields.graphql_gf_form_field_value_properties filter in favor of graphql_gf_form_field_value_fields.FormsConnectionResolver to use new AbstractConnectionResolver methods.automattic/vipcs Code Standard ruleset.submitGfForm mutation.formId with id in submitGfForm examples. Props: @mosesintechFull Changelog: https://github.com/harness-software/wp-graphql-gravity-forms/compare/v0.11.11...v0.12.0
This minor release fixes a bug where the provided IP address was not saved correctly when using the submitGfForm mutation.
Full Changelog: https://github.com/harness-software/wp-graphql-gravity-forms/compare/v0.11.10...v0.11.11
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.
Full Changelog: https://github.com/harness-software/wp-graphql-gravity-forms/compare/v0.11.9...v0.11.10