chris10011

Doesn't seem directly like a supabase issue but I can offer some advice. If your application is using a replicated local database enumerated types typically do not replicate directly. Usually you create a function in your schema to expose the values of the enumerated type, for example: ``` select array( select unnest(enum_range(null::sales.priortity))::text ); ``` (that would be a named function on your schema). Then your client would call that to see what types are available. Your issue isn't completely clear to be honest, but I hope this gets you on the right lines.

Just a quick one to check, but if you're on a VPN try disabling it.

https://supabase.com/docs/guides/api/custom-claims-and-role-based-access-control-rbac

Is there any reason RLS might not work with better auth? RLS is usually based on a custom claim / roles in your JWT token, which is agnostic to how you're handling auth.

This doesn't seem relevant to supabase but I actually do know what is probably causing this for you. Sharepoint does not actually allow HTML documents to be rendered usually, especially when they have any from of <script> tags. You have to enable this option within legacy sharepoint, and it turns it self off after 24 hours, so if you are continuously uploading this document it's a massive pain. I think its possible to update with powershell, but it's poorly documented (as is any microsoft product). Good luck

Hopes this helps someone. These are not issues caused by supabase but in my opinion will affect a lot of developers using supabase.

https://github.com/denoland/vscode_deno/issues/1269 To solve problems not showing for all files in the repo, add " "deno.forcePushBasedDiagnostics": true to your settings.json

Problem 1. solved by https://github.com/denoland/vscode_deno/issues/1317 . Problem 2 seems like intentional behaviour from deno, however will continue to investigate.