#liam_elements-react
frozen swiftBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1303043869088284805
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- liam-hunt-bonterra_docs, 5 days ago, 19 messages
- liam_paymentelement-link, 5 days ago, 22 messages
terse cove
liam_elements-react
@echo flint the easiest would be to just try and see what happens, should take only a few minutes locally to get your final answer
echo flint
The app renders without error with two <Elements> components present. I was mainly wondering if this is considered a dangerous pattern or against best practices
terse cove
I don't think it's dangerous no. I've seen people do this to have an element for their own payment and one for payments on a connected account for example
echo flint
Ok thank you. I appreciate the help.