useSqPaymentForm Hook

[garand]

Thanks for working on this library! It's been super helpful for me. Would you have interest in also including a hook? I needed to do some things that the component didn't let me do and also liked the hook approach for this in my use case so I built one.

https://gist.github.com/garand/9403725af3ef3ff3f7047df28581b1ff

I would love to contribute it back to the project if it's something you'd be interested in.

Thanks!

[garand]

I've vastly improved the hook linked in the Gist above. It has been re-written with TypeScript and has an associated .types.ts file that pulls types from https://developer.squareup.com/docs/api/paymentform.

I have yet to add documentation for how to use it, but that's something I can do if you'd be interested in folding it into the project.

[stephtaylor]

Hey @garand! Sorry for the delay. Definitely wish I knew about hooks when this library was first published so I'm open to hearing about using a hook approach instead :)

I already see some advantages with hook you built, but I'm curious to hear some of the use cases you weren't able to accomplish with the current library.

Biggest concern for me would be around the potential need to maintain both a hook solution & a component solution. However, there's probably a good code-sharing solution and it might even make sense to only have a hook solution going forward (the library requires hook support anyway).

[garand]

@stephtaylor Originally my use case was to be able to set inputClass, but that was since added. #55

The hook approach, to me, feels more idiomatic and lets me handle the integration exactly how I need and doesn't add any styles so I can control that all myself. It looks like a lot has been added and updated since April though! That was the last time I used the library.

On your concern about duplicate code for the hook and component solution, if it were me I would make the hook be the engine powering this project. Export the hook so someone can use that, but also build the component approach and have it be powered by the hook for those that don't need all the complexity and configurability that the hook would provide.

[jelizarovas]

This! ^^^^ Right now most of the react libraries or packages are transitioning to hooks. It's just that much simpler to understand and use. I'm trying to make an app where we can charge customers on site after service has been completed. Right now we use square app to charge, but would like to combine into single source. It seems like stripe.js has a much easier onboarding process and they're using hooks.