Adding support for Ecto embeds_one feature

[fcbry]

Hi, I’m on my phone, so please forgive formatting..

In some cases it is advantageous to have the ability to add extra configuration to an entity without having to modify the database schema. EmbeddedSchema with embeds_one can be very useful here.

https://hexdocs.pm/ecto/embedded-schemas.html#user-profile-example

In my specific case I am developing a module for a school management system, let’s say it’s a School, that integrates with a bunch of other school management systems, let’s say there are dozens of such systems and each one requires its own config (url, encrypted token, etc, etc).

it’s not open ended in the sense that it would make sense to have a separate table for the integrations, but it is open ended in the sense that each integration with require some arbitrary number/type of fields.

I’ve managed to model for a single case using virtual fields and some convoluted mapping logic and can repeat this for the next 6 integrations without too much hassle (copy and paste + LLM) but the pattern seems ugly.

It would be nice when defining my LiveResource I could so something like:

use Backpex.LiveResource,
  # ...
  fields: 
  [
    # maybe expressing path with array or tuple
    [:powerschool_integration, :api_key]: %{
      module: Backpex.Fields.Text,
      label: "Rating"
    },
    # another 30 embedded fields here
  ]

Then in my Ecto (pseudocode)

SchoolConfig 
   embeds_one powerschool_integration…
   embeds_one otherschool_integration
   etc etc

i hope that makes sense

[io2]

Are you building a single use solution (i.e for one School's needs) or more of a saas product?

I have been working on a School Management platform using Elixir, we should talk :)