Open PeterNerlich opened 2 weeks ago
@PeterNerlich Thanks for this issue. What do you mean by message list? This one: https://integreat.app/testumgebung/de/news/local
@ztefanie Yes, that one
@PeterNerlich do you know whether we should filter out news that are older than 28 days? Or should filtering still be done exclusively in the CMS? If we filter in the apps, we'd have another place we'd have to adjust this time period if we ever decide to change it. I also remember some discussions about that.
@nikolahoff Furthermore, our last update timestamp should also reflect the same logic (i.e. lastUpdate = max(sent, last_modified)
), correct? Otherwise just sorting differently could still confuse if the sorting behavior is not comprehensable.
@PeterNerlich do you know whether we should filter out news that are older than 28 days?
I have not worked on this part of the API and don't know past discussions around that, but as we do already limit which results we put out, so there is no need to do that on app side. This issue is only about sorting, e.g. when news are edited and should thus appear as recent again.
Is your feature request related to a problem? Please describe.
Sometimes push notifications that are older than 28 days appear in the message list / seemingly out of order. This is confusing.
Describe the solution you'd like
max(last modified, sent)
timestamplastUpdate
tomax(last modified, sent)
timestamp` (TBD)lastUpdate > 28 days
Describe alternatives you've considered
Leave it as is
Additional context
This was discussed in the Integreat CMS team, we concluded that there is nothing in our API that would influence this and it has to be implemented on app side.