PointSource

Detecting serialization methods would be a much more dynamic solution and would possibly solve support for much more than FIC. That said, it's certainly not trivial to make something so...

The original issue was on a different codebase with different path vars. I will check this again and ensure the path var names are identical in both the original occurrence...

I have confirmed that the same exception still occurs after correcting the "subID" to "subId". I have also updated the issue to reflect this.

Hmm seems this doesn't result in valid openapi spec under some conditions. Will continue to work on it. Don't merge yet.

Okay, this should be safe now. Actually maybe safer than the original implementation and I confirmed it still works with the openapi sdk generator. It is also much clearer about...

After more testing, it looks like using `MapperContainer.globals.toMap(object)` does not include the `__type` key in the output but using `MapperContainer.globals.toMap(d)` does.

When creating a library which does not have a main method, such as one for communicating with an API, should `initializeMappers()` be called when the class is constructed or somewhere...

As this is currently blocking an issue on my project, is there a better way to determine whether a function is being called by an authenticated user vs an edge...

Would that new docker image be released already or is it still in a pipeline somewhere? I pulled latest yesterday and am still getting "postgres" as the session_user

@barbinbrad Well you can sort of workaround it by changing the $POSTGRES_USER env variable on the db container but that's not particularly streamlined vs running the supabase cli