Refactor/project restructure

[zoedsoupe]

Problem

The first version of the project was a PoC of the architecture of Supabase.Client and the old Supabase.Connection modules.

The old structure of this library was to split Supabase integrations completely different and independent applications. That idea wasn’t discarded but somehow put in the “backlog”. Indeed, a “monolith” implementation of all-in-one library makes more sense for the current project status as somethings are not well defined, for example the Supabase.Phoenix.UI future module. So i took the decision to splliting applications as soon as they grow and maybe become an underwhelmed library as the same time that you want to use Supabase.Storage it will download and compile all Phoenix stuff. That doesn’t make sense for all. To sum: until the library could coexist in single package it will, but in the future it will be splitted.

Solution

• merge again all umbrella apps
• discard the idea of multiple Supabase.Connection and prefer only multiple Supabase.Client, that now owns a :conn field
• Use a Registry by default to organize and make it simple to lookup for Supabase.Client PIDs
• refactor Storage implementation to use Supabase.Client and handle errors in a better way
• improve documentation

It’s imoprtant to note that the “base API” or the main API that this library exposes didn’t change for compatibility reasons and the “upgrade” from those apps spllited to this all-in-one will be easy peasy like lemon squeez.

The higher and most important chenge is the absence of Supabase.Connection for the current version as it is part of Supabase.Client struct/Agent. That means that the Supabase.init_connection/2 was discarded and Supabase.init_client/2 does not receive a list of connections anymore, as you can pass connection details directly to the Supabase.init_client/1:

Supabase.init_client(%{conn: %{base_url: “”, api_key: “"}})

There’s also a bang version of the Supabase.init_client!/1 that will try to fetch connection details from the :supabase application config, that can be set up on a config.exs or runtime.exs. If it fails on fetching an error will be raised and documentation will be printed on how to find these connection details.