Flop.Phoenix - UI components for pagination, filter forms and sortable tables

Flop Phoenix 0.24 is out. This and the next releases will focus on cleaning up some cruft that was accumulated over the years. The first version didn’t even consider LiveView, and we were all still writing content tags back then. Some early design decisions turned out to be a bit awkward in LiveView years later. On the road to 1.0, I’ll try to get rid of that baggage. The second focus will be to rethink the approach to component customization.

Highlights in 0.24 are new features to facilitate building custom pagination components in case the default pagination component doesn’t fit your use case, as well as some extensive internal refactoring.

Full changelog:

Flop.Phoenix 0.18.0 was released. Apart from some under-the-hood updates, the main change is the updated filter_fields component, which now produces the Phoenix.HTML.FormField struct introduced in Phoenix.HTML 3.3.0.

This release deprecates Flop.Phoenix.pop_filter/2 in favor of the updated Flop.Filter.pop/3 function, which will be released with Flop 0.20.0 soon.

Flop Phoenix 0.20 introduces on_paginate and on_sort attributes for executing JS commands during pagination or table column sorting. This can be used for scrolling the top of the table into view when paginating, for example. An example for exactly that use case can be found in the documentation.

It’s also possible to dynamically set row and cell attributes depending on the current row item now.