Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove timeout removal, remove component unmount #196

Merged
merged 2 commits into from
Feb 21, 2021
Merged

Conversation

hartzis
Copy link
Collaborator

@hartzis hartzis commented Nov 23, 2020

Attempt to fix #171.

Additionally:

@dozoisch could you possibly publish an alpha/beta of this that I can test?

馃摀 If this does all work and simplifies things it will possibly require a major? 馃

@dozoisch
Copy link
Owner

Yep will publish today

@dozoisch
Copy link
Owner

Published from this branch 3.0.0-alpha.1

@hartzis
Copy link
Collaborator Author

hartzis commented Nov 25, 2020

@dozoisch Thank you thank you!

I was able to validate that #171 appears to be fixed using the example the author created

I also validated against our two other codesandbox examples that this change doesn't break anything

Curious about your thoughts on the release. I'm starting to think that this change is actually backwards compatible, maybe a major is too conservative?

Maybe only a minor and if it does break we can hotfix with a bug fix?

@anajavi
Copy link
Contributor

anajavi commented Dec 18, 2020

If you are releasing a new major, the react dependency could be bumped to 16.14.0 too.

That would enable the use of the new jsx transform

@dozoisch
Copy link
Owner

@hartzis sorry for delay.. im tempted to still go for major given the change underneath and take the opportunity to do other major bumps like that react bump

@hartzis
Copy link
Collaborator Author

hartzis commented Dec 19, 2020

@dozoisch i think either approach is fine, but the major is definitely safer.

i also like the thought @anajavi has about bumping the react version

@romainleduc
Copy link

romainleduc commented Feb 20, 2021

Hello, this PR seems to have solved an issue I'm currently experiencing.
Is it expected to merge soon ?

Currently I have to proceed in this way to see the recaptcha badge displayed

const formReCAPTCHA = () => {
  const [load, setLoad] = useState(false);
  
  useEffect(() => {
    setTimeout(() => {
      setLoad(true);
    }, 5000);
  }, []);
  
  return (
    <form>
      {load &&
        <ReCAPTCHA
          ref={recaptchaRef}
          size="invisible"
          sitekey="6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI"
        />  
      }
    </form>
  );
}

Thank you :)

@dozoisch
Copy link
Owner

@romainleduc for the time being you can set your package.json version to 3.0.0-alpha.1 to have this fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invisible captcha badge not rendering again after just unmounting
4 participants