This component is fantastic and has made life a lot easier, the issue I am having is when using a radio field. The user is able to select multiple options and cannot deselect any options they have clicked on.

I am using the latest gravity forms plugin http://2.5.3.1/ and am using the example component found in the readme. Could I have set something up incorrectly?

Any help would be appreciated.
thanks!

I get the following error when trying to send the form.

Uncaught (in promise) TypeError: Cannot read property 'confirmation_message' of null at _callee$ (index.js:98) at tryCatch (runtime.js:45) at Generator.invoke [as _invoke] (runtime.js:274) at Generator.prototype.<computed> [as next] (runtime.js:97) at asyncGeneratorStep (asyncToGenerator.js:3) at _next (asyncToGenerator.js:25)

Lambda expects the user to use Netlify/AWS but an endpoint could be anywhere.

Update argument to be called "endpoint" or something more friendly to stop confusion.

Also update readme explanation to reflect this

import useForm from 'react-hook-form/dist/react-hook-form.ie11'

https://react-hook-form.com/faq

Radio and checkbox inputs that are set to required always fail validation. They are able to pass if and only if all checkboxes and radio buttons are selected. Another issue with the radio buttons is that you can select multiples of them. This goes against the expected user experience.

Versions that i'm running:

"gatsby-source-gravityforms": "^1.0.15"
"gatsby-gravityforms-component": "^2.0.1"

You reference gatsby-gravityforms-components (plural) several times in your readme, but It looks like your package is singular npm i gatsby-gravityforms-component

Thank you for this project! I'm trying to implement it now on a project, hopefully this will work otherwise I'll need to explore Netlify forms. If i had the luxury of time I'd help you out with this!

You also mention that gatsby-plugin-compile-es6-packages is included as a peer dependency, but it doesn't look like it is included. I had to install it separately.

When I run a gatsby develop, I receive the following errors:

• Unknown field 'subLabelPlacement' on type 'GF__Form'. Source: document 'GravityFormComponent' file: 'GraphQL request'
• Unknown field 'disableAutoformat' on type 'GF__Form'. Source: document 'GravityFormComponent' file: 'GraphQL request'
• Unknown field 'captchaTheme' on type 'GF__FormFormFields'.

Removing these fields fixes everything for me. Am I missing something? I can't find these fields in your other plugin (which is awesome, btw) gatsby-source-gravityforms, so it makes me think that my version of Gravity Forms is missing some fields in the API.

I'm running the latest version of Gravity Forms (2.4.17.17) and the latest versions of both of your plugins.

Currently when formLoading is true this span is replacing the button text:

I'm proposing adding a prop to allow anyone to pass in whatever they want for the loading span or optionally have no loading span at all.

I just want to pass in a loading spinner instead of just having the word "Loading" in the button text.

Bonus if we could replace the button component altogether.

When submitting a form entry, I receive this error:

POST websiturl.netlify/functions/newGFEntry 422

It doesn't seem to access the file properly as none of the console.logs are happening either.

Just realized I need this for my client. I'll be working on it but wanted to give you a heads up. If you have any input, suggestions, etc...would love to hear it. Thanks.

Every instance of this component produces the below warning:

Warning: Failed prop type: Input: prop type `maxLength` is invalid; it must be a function, usually from the `prop-types` package, but received `undefined`.
    in Input (created by FieldBuilder)
    in FieldBuilder (created by GravityFormForm)
    in form (created by GravityFormForm)
    ...

Here is a sample instance that consistently produces the warning:

<GravityFormForm
	id={1}
	formData={useGravityData()}
	lambda={process.env.GATSBY_LAMBDA_ENDPOINT}
/>

This is not a breaking issue. Maybe I am missing something, but this looks like a simple prop discrepancy bug. Documenting it here, but I may visit the code and open a PR if I have time.

Hey, it would be nice if the forms were rendered with the Gravity Form classes so Including their style sheet gave me the same styling as if this were in WordPress. I might be able to help contribute this if you'd be willing to accept the PR. Thanks.

Hello.
When submitting form on development, getting following error:

Request from ::1: POST /.netlify/functions/newGfEntry
Response with status 500 in 0 ms.
Error during invocation: TypeError: a is not a function
at Object.t.handler (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/lambda/newGfEntry.js:1:37305)
at /Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/netlify-lambda/lib/serve.js:146:27
at Layer.handle [as handle_request] (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/layer.js:95:5)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:137:13)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)
at next (/Users/hryhoriiroiwork/Documents/Roi New Website/roi-mediaworks-website/node_modules/express/lib/router/route.js:131:14)

Do you know why can it happen?

Line 52, and 57. Should be restResponse