Add traditional pagination to both admin bridges

[ahmed-bhs]

Q	A
Bug fix?	no
New feature?	yes
BC breaks?	no
Fixed tickets	#59
License	MIT

Summary

This PR adds traditional pagination to both EasyAdmin and Sonata Admin bridges, addressing performance issues when browsing large media libraries. Previously, all media items
were loaded at once, causing slow page loads and high memory usage with libraries containing hundreds or thousands of files.

This implementation uses native pagination components from each framework to ensure a consistent UX that follows admin interface conventions.

Changes

EasyAdmin Bridge:

• Add MediaPaginator adapter compatible with EasyAdmin's pagination system
• Use native @EasyAdmin/crud/paginator.html.twig template
• Remove infinite scroll feature (not standard in admin interfaces)

Sonata Admin Bridge:

• Add MediaPager implementing Sonata's PagerInterface
• Create pagination templates based on Sonata's native components
• Server-side pagination with configurable items per page

Common:

• Configuration option pagination.per_page (default: 50)
• Improved performance for large libraries (hundreds/thousands of files)
• Consistent pagination UX across both admin frameworks

Configuration Example

joli_media_easy_admin:
    pagination:
        per_page: 50  # Number of items per page

joli_media_sonata_admin:
    pagination:
        per_page: 50  # Number of items per page

[xavierlacot]

Hi @ahmed-bhs

Thanks a lot for this first contribution that relates to #52 👍

While I appreciate it a lot, may I ask for some changes?

• first, the quality tools have to be executed, so the tests turn green. You can use the castor qa:all command to check for errors.
• second, I am not sure that infinite pagination is a good UX pattern in the admin bridges. Neither EayAdmin nor Sonata Admin natively implement infinite pagination. May I ask you to remove the infinite pagination feature (and the assiociated js code) and instead use a traditional pagination, possibily using the native EasyAdmin pagnination component, to ensure a coherent UX? I am a but annoyed to request the removal of some code that must have taken you time to write, but I think it is the best way to go. Maybe should we explain in the contribution guidelines that is is a good idea to request for advice prior to submitting a UX change pull request?
• third, the bundle aims to offer comparable levels of functionality between EasyAdmin and Sonata Admin. May I ask to add identical features in the Sonata Admin integration? You can use the demo application to test - see https://mediabundle.jolicode.com/getting-started/demo/#using-the-demo-application-to-contribute-to-jolicode-mediabundle

Thanks again!

[ahmed-bhs]

Hi @xavierlacot , nice to meet you and thanks for taking the time to review!

I originally developed this feature for my own needs and thought it would be nice to share it as a pull request rather than keep it private. Don't worry at all about the code removal. I completely understand your point about maintaining UX consistency with the native admin frameworks. It makes total sense!

All requested changes are done. Still unsure about using EasyAdmin and Sonata’s native pagination—this part need to be reviewed.

[BriceFab]

->getInt() could be used here?

[ahmed-bhs]

Good catch @BriceFab tank you

[xavierlacot]

Thanks for the hard work @ahmed-bhs 🎉