Disabled Prop

[twdrake-ap]

I have a situation where it would be nice to have the flexibility to pass a disabled prop to the PSClickWrapContainer. Is that possible? Right now I'm required to hide the component until a valid signerId value has been entered into a signup form.

Somewhat related, was a signerIdValue prop ever considered to be used in place of signerIdSelector? Would be a nice option to have.

[kylepeeler]

You should be able to set the signerId prop to pass the value of the signer id as opposed to using the signerIdSelector. If you have issues using that, I just realized I may need to update the componentDidUpdate function of the component to persist changes after initial render to the signerId prop. I'll push an update shortly so you should be able to update that value dynamically and have the signerId render.

As for the disabled prop, theres a few options,

• You can set the displayAll prop to false which will only load the contracts that the signer has not already signer. Without a signer id present it should hide the contracts.
• You could do conditional rendering based on state of your app to only load the PSClickwrap when it makes sense, something like: {this.state.hasSignerId && <PSClickWrap ... />}

If either of those two options don't work out, I'll try and get a shouldDisplay prop that hides or shows the clickwrap group in the next release.

[kylepeeler]

I just pushed v2.1.0 which should have a fix so you can use the signerId prop and _ps will reflect the current value of the signerId prop even if it is updated after initial render (e.g. updated in the parent component via state).

Keep in mind every time this value is changed we make a call to our servers, and as such if it is changed in a very short period of time (e.g. a state prop that is tied to user input), you may easily hit a rate limit. If it is tied to user input, it is best to tie this value to update when the user is done editing (e.g. tieing the update to onBlur as opposed to onChange) to ensure this is never hit. However even if the rate limit is hit, the correct signer id will still be sent to the server on agree (usually the rate limit will time out by the time they go to check the box) so you should be good to go 👍 .

Let me know if you run into any other issues, as for the disabled prop I need to spend a bit more time on that and should get it into v2.2.0 sometime next week.

[twdrake-ap]

Awesome, thank you! Yeah the disabled prop would solve our current issue where we want to display our 'agree to terms' checkbox, but not let the user click/check it util the form that it is attached to is completely filled out. We currently use the 'combined' layout...