Tobias Barsnes

> We have not out of nowhere gotten new problems with vercel, where it can't route anything. > > > I think we should prioritize this To fix this we...

We have now gotten access to Azure, and will be testing it this week

Azure seems to work fine: https://www-test-ca-app.victoriousglacier-eb9399b9.norwayeast.azurecontainerapps.io/no The above url is only a test URL, being deployed form a docker image. One thing that is also **very nice**, is that everything...

Everything is now working for previews in #4010, but we can't test production deployments properly before we merge it into main. We don't use custom domains for preview deployments anymore,...

we are now on Azure. Domains remain on Vercel. For now.

I suggest we change the check to: ```ts if ( !Children.only(children) || children?.type === Fragment || Children.count(children) > 1 ) { console.error( ' children needs to be a single ReactElement...

> See your suggestion, but this will break if passing nested Fragments for instance passing: > > ``` > const Group (props) => {props.children}; > > render(Content); > ``` >...

I tried doing this with the check we have today, and the tooltip is rendering fine. Could you send a snippet of your component? ```tsx const Group = forwardRef( ({...

> Both of these will work fine ☝️ But thats only because Group renders a div. If Group renders only a Fragment, it will not work. Therefore I sugges checking...

It's also not documented in storybook, since nothing is documented (😓 ), but the component you pass as a child needs to be able to recieve a ref