The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
See #3618286: List "Flippy" as simpler (less powerfull) alternative?
Seems like they already solved a lot of the 3.x points, but maybe don't have all the flippy features yet plus not that simple UX?
Comments
Comment #2
anybodyComment #3
joachim commented> but maybe don't have all the flippy features yet plus not that simple UX?
It's true that Entity Pager requires you to create a view for your pager, so to create the same thing as Flippy, you'd need to create a view, add a node type filter, and then place the block.
I'm looking at adding computed field support so the pager outputs as a field -- #3619359: add Computed Field support.
As for pager creation DX, we could feasibly add an admin UI that creates a template view for an entity bundle pager.
Comment #4
joachim commented> As for pager creation DX, we could feasibly add an admin UI that creates a template view for an entity bundle pager.
It's a shame that there's no longer the default views hook, as that would be one way to do it.
Comment #5
joachim commentedSpurred on by this, I've started working on a module for fixed config. It's something I've had on my mind for a long time.
It would allow this module to depend on Entity Pager, and then define derived fixed config which automatically makes a view for each node type.
Comment #6
anybodyThanks @joachim please keep us updated here. We're open for any useful path.
Still I think if joining forces with entity_pager I'd fully like to deprecate flippy (and if possible provide an update path here).
Comment #7
joachim commentedI was thinking Flippy could stay as a project that depends on Entity Pager, to provide automatically-configured node type pagers.
Comment #8
anybody@joachim Yes, I’d already thought you might mean that, but I believe it would be better for users if they only had to use `entity_pager` and the relevant functions were integrated into it. I think Flippy would then become obsolete and can be deprecated.
Comment #9
joachim commentedWith Composer for package installation and a dependency for Drupal installation, it would be transparent to users - they'd just install Flippy as they currently do.
I wouldn't want it in the main Entity Pager module, and the problem with having it as a submodule is that it will have Fixed Config as an additional dependency, so Composer won't install it.