Looks great!
Wanted to ask if you have considered using a protocol or behavior that then uses Ecto.Schema to easier allow integrations such as Ash?
Kallee
3
virinchi_cv
Thanks!
I haven’t used Ash till now. While I might take it up in the future, its not currently on the todo list.
Would be more than happy if anyone raises a pull request though! 
1
virinchi_cv
LiveTable v0.3.0 is out!
Hello Elixir community—
Excited to announce the release of LiveTable v0.3.0, with several game-changing new features including Transformers,Custom Queries & Card Mode.
Hex Link- LiveTable
Read the full article: LiveTable: Real‑Time Data Tables in Elixir · Virinchi's Blog
Try it out now!
An Advanced Demo of LiveTable with Custom UI, Card Mode, Transformers & Custom Queries:
Read the Full article here: Turning JEE Counselling Chaos into a LiveView Showcase · Virinchi's Blog
Looking forward to seeing what you build with LiveTable v0.3.0! 
7
virinchi_cv
LiveTable v0.4.0 is out! 
Generators, Infinite Scroll, 0 external js dependencies and so much more!
Check out the full Changelog.
Revamped Live Demo with 1M rows of data: LiveTable Demo
Owing to the opinionated nature of open-source frameworks these days, we have made a conscious decision to move away from Daisy UI, and instead, use Sutra UI - a shadcn inspired UI framework written in Pure Phoenix with accessibility in mind.
Alternatively, if there are any daisy users, they can opt to use our custom_ components to mimic those in table_component.ex and use our functionality without any of our UI.
Try out LiveTable today- {:live_table, "~> 0.4.0"}
Looking forward to seeing what you build with Livetable!
2
reimu
Congrats on the release! I tried to upgrade from 0.3.1, but it seems Sutra UI needs to be properly installed which involves a lot of setup and is incompatible with the default Phoenix components.
It seems to require more maintenance now, so could you share how you expect other devs to integrate LiveTable in their project?
1
virinchi_cv
LiveTable requires Sutra as its dependency.
Devs have 2 options to use Livetable-
- Use the default LiveTable UI: Add sutra, remove core_components.ex, follow instructions in Sutra setup - and use LiveTable with Sutra. This is the recommended approach.
- Dump LiveTable’s UI, use your own: You can dump out the UI, and define your own components to mimic those of LiveTable - and pass them using the custom_component method. Most suited for devs with other css/styling frameworks.
Either way, you get all features right out of the box. Exports, URL params etc.
You can use Sutra’s installer task to get set up & running quickly.
0
bruno_louvem
First off, congrats on the library @virinchi_cv I’m really excited to start using it.
My project currently runs on DaisyUI. I noticed in previous comments you mentioned it’s possible to use live_table without sutra_ui, but currently, sutra_ui is listed as a hard dependency in mix.exs. This means it gets installed and compiled even if we don’t intend to use it.
Would it be possible to mark sutra_ui as optional: true in the next release? Or perhaps provide a small guide/snippet on how to configure live_table (v0.4.0) to use a custom renderer (like DaisyUI) without pulling the Sutra dependency?
Thanks for the great work!
1
virinchi_cv
Thanks @bruno_louvem! 
Sure- will make Sutra UI optional in the next release.
There isn’t an explicit guide on how to dump the entire UI - will add it in the next release. Its described for just the header in the docs. You can read more from the custom header docs.
But the process is pretty straightforward.
Taking a look at table_component.ex, its pretty easy to understand how it works. Just define each one - header, footer, content as custom_ and pass it via table_options.
You can use Daisy or virtually any styling in the custom_components.
1