My company has early-adopted Flop & Flop.Phoenix in May 2021 and we have been using it for admin dashboards in multiple apps since, in production environments. We especially love the sweetspot position Flop.Phoenix takes between “being a logic-less table component” and a full-blown UI generator, giving us enough out-of-the-box functionality while allowing for easy customization. It’s been working like a charm and @woylie has been very generously devoting time to the issues we’ve raised and ideas we had.

Sounds a bit like an advertisement ^^ What I’m trying to say is: This pair of libraries deserves a lot more attention.

Thank you @woylie for all the work

Flop 0.19 comes with custom fields, a new helper for dynamically adding bindings, and a set of filter manipulation functions.

Added

• Support for custom fields. These fields allow you to run custom filter
  functions for anything that cannot be expressed with Flop filters.
• Added Flop.with_named_bindings/4 for dynamically adding bindings needed for
  a Flop query.
• Added fetch, get, get_all, delete, delete_first, drop, new,
  take, pop, pop_first, put and put_new functions to Flop.Filter.
• Added Flop.Meta.with_errors/3.
• Added ecto_type option to join fields.
• Added not_like and not_ilike filter operators.
• Added a cheatsheet for schema configuration.

Changed

• Renamed Flop.bindings/3 to Flop.named_bindings/3.
• Flop.Filter.allowed_operators/2 now tries to determine the Ecto type by
  reading the Flop field type from the schema module. This function is used
  during parameter validation, which means the validation step will be a bit
  stricter now. For join and custom fields, the Ecto type is determined via the
  new ecto_type option. If the option is not set, the function returns all
  operators as before. For compound fields, only the supported operators are
  returned.
• Added opts field to Flop.Meta struct.

That is already implemented! You can choose between offset-based and cursor-based pagination. See also:

• pagination parameters
• more pagination examples
• Flop.Cursor
• Flop.Relay

Flop.Phoenix has two different UI components for offset-based and cursor-based pagination.

• pagination component
• cursor pagination component

Flop 0.20.0

Added

• Added Flop.unnest_filters/3 as a reverse operation of Flop.nest_filters/3
  after retrieving data from the database.
• Added Flop.Filter.fetch_value/2, Flop.Filter.get_value/2,
  Flop.Filter.put_value/4, Flop.Filter.put_new_value/4,
  Flop.Filter.pop_value/3 and Flop.Filter.pop_first_value/3.

Changed

• Several of the functions for manipulating lists of filters in the
  Flop.Filter module now accept lists of maps with atom keys, lists of maps
  with string keys, and indexed maps as produced by Phoenix HTML forms as
  argument.
• The empty and not_empty operators now treat empty maps as empty values on
  map fields and empty arrays as empty values on array fields.
• % and _ characters in filter values for the like, ilike and =~
  operators are now escaped.

Fixed

• Fixed an issue that caused filter conditions for like_and, like_or,
  ilike_and and ilike_or to be incorrectly combined when applied to compound
  fields.

[0.20.2] - 2023-06-09

Changed

• Added nutrition facts about use Flop and @derive Flop.Schema.
• The minimum Elixir version is now 1.11.

Fixed

• Fixed a deprecation warning about Logger.warn/1.
• Fixed a deprecation warning about passing an MFA to :with in
  cast_assoc/cast_embed introduced in Ecto 3.10.2.