activity wall only shows latest entry per fsp,buddy, event wall
What does this MR do?
Foodsharepoints are grouped so that in the activity overview only newest entry per fsp is shown. Buddy wallposts are grouped so that in the activity overview only newest entry per buddy is shown. Event wallposts are grouped so that in the activity overview only newest entry per event is shown.
How confident are you it won't break things if deployed?
quite
Links to related issues
Any relevant links (issues, documentation, slack discussions).
How to test
Steps a reviewer can take to verify that this MR does what it says it does e.g.
- Checkout branch locally
- Login as foodsaver
- Go to your activity updates
- Filter for FSP
- You should see just one line per fsp
- Create an event
- make some comments
- check the activity wall
- login with userorga
- create some profile posts
- switch to userbot and check activity wall
HINT - as the seed data it can happen that old dates are stored in a newer Wall_id , this should not occur on production.
Screenshots (if applicable)
before:
After :
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
set a "for:" label to indicate who will be affected by this change -
use "state:" labels to track this MR's state until it was beta tested -
added an entry to CHANGELOG.md -
add a short text that can be used in the release notes -
Once your MR has been merged, you are responsible to create a testing issue in Beta Testing Repo: - Consider writing a detailed description in German.
- Describe in a few sentences, what should be tested from a user perspective.
- Also mention different settings (e.g. different browsers, roles, ...). how this change can be tested.
- Be aware, that also non technical people should understand.
Release notes text
Auf der Aktivitätsübersichtsseite im Dashboard wird nun von Event-, Fairteiler- und Buddypinnwänden nur der letzte Eintrag angezeigt.
(A short text that will appear in the release notes and describes the change for non-technical people. Not always necessary, e.g. not for refactoring.)