Add pagination on past events

[srosset81]

It causes performances problems

[Laurin-W]

To understand the issue correctly, does this occur when fetching from /:user:/events?
Testing on my local machine, for 116 events, the request took 4-7s.

I'm not sure what kind of implementation direction this would take. Three came to my mind right now:

1. Use a URI parameter to filter events from the past
2. Implement LDP Paging spec
3. Implement [ActivityPub Paging] as done for the in/outboxes as well.

Do you have a preference for either or were you thinking of something else?

[srosset81]

The idea would be to first implement pagination on the frontend, so that not all events are shown. React-Admin has a component for this which could be used out-of-the-box:
https://marmelab.com/react-admin/doc/3.19/List.html#paginating-the-list

With this solution, all events will be fetched (because we haven't found an easy way yet to paginate SPARQL query results) but at least they will not all be rendered. On old mobile phones, rendering many events can take many seconds.

But it's true the optimal solution would be either:

• Adapt SPARQL queries to take into account pagination. Right now it is done afterward, see https://github.com/assemblee-virtuelle/semapps/blob/master/src/frontend/packages/semantic-data-provider/src/dataProvider/utils/fetchSparqlEndpoints.js#L100-L119
• Use LDP containers pagination (we have discussions about this here Implement LDP paging assemblee-virtuelle/semapps#176 but unfortunately they are in French. Hopefully some automatic translators can help you). Right now it is done here: https://github.com/assemblee-virtuelle/semapps/blob/master/src/frontend/packages/semantic-data-provider/src/dataProvider/utils/fetchContainers.js#L94-L112