Thanks! I believe I needed it because of controller/html files

I’m sure there is a way to render these without depending on liveview, but it was the easiest route to take for the initial release

This is awesome. Initial question, is there a particular reason it’s dependent on LiveView 0.18?

Very cool project!

I’m attempting to add it to my ash project but running into an issue. The preloads don’t work with ash because the type of missing preload fields is Ash.NotLoaded instead of the corresponding ecto struct. Maybe there is a way to externalize the preloading operation so someone can optionally plug in their own preload function, defaulting to repo.preload as is the case now.

A nice-to-have would be to allow for separation of the application’s user and local stripe customer records so each of these records can live in different contexts/domains and not require fetching the billing info (stripe_id, etc…) when it’s not needed. I tried to achieve this but ran into an issue because the updates to the user record require the fields to be on the same schema as the customer’s email address.

Looking forward to continued development on this project!

Edit: I was able to work around the first issue by implementing a proxy Repo module which is implemented by calling ash and providing this proxy repo to bling instead of the underlying ecto repo module.