David Lorenz

We've got the exact same problem which makes our `e2e` tests literally unusable. A workaround is to create a wrapper component that uses that component but that's massive work.

Also the proposed workaround is not really a workaround if you have `mdx` files as those seem to require the docs. For good reason.

Update: Downgrading to `@compodoc/[email protected]` "fixed" it for us. All other versions broke the application. So update your package.json to `@compodoc/compodoc: "1.1.11"`

I noticed you CAN add a FK here. But it is not intuitive. It's the Link Icon.

The separation is a good step already. I'm unsure about link vs key icon. Could you imagine something with a pointer/arrow somehow indicating it's pointing to somewhere? like an arrow...

Awesome, seen that, works well.

So kinda I criticize what's been improved already. So I guess we can close this. Probably didn't notice it because it's not yet deployed in my latest package as it's...

But one question remains open: Wouldn't that still leave the problem open of still technically being able to do OTP? I'd like to be able to disable those (but I...

https://supabase.com/docs/reference/javascript/next/auth-signinwithotp I think this should be extended to fit your needs: `signInWithOtp({..., shouldCreateUser: true, onCreateUserData: {your_meta_data}})`

You guys are the best!.