We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug If you don't put LoginButton into it's own container and try to conditionally render, it will stay after the first render forever.
To Reproduce Steps to reproduce the behavior:
Expected behavior Not rendering LoginButton results in no button
const [click, setClick] = useState(false); return ( <> <Button onClick={() => setClick((v) => !v)}> click </Button> { click ? <Button> Feed </Button> : <LoginButton botUsername={} authCallbackUrl={} buttonSize="large" cornerRadius={5} showAvatar={false} /> } </> )
The text was updated successfully, but these errors were encountered:
Thank you for reporting the issue. #28 should fix it.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
If you don't put LoginButton into it's own container and try to conditionally render, it will stay after the first render forever.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Not rendering LoginButton results in no button
The text was updated successfully, but these errors were encountered: