Remove unused GraphQL endpoint and ff
What does this MR do and why?
This code change removes an experimental activity stream feature from the GraphQL API that was introduced in !183872 (merged). The feature allowed users to view recent activity from people they follow, including events like project joins, issue updates, and other user actions.
Note: It was only used in the prototype and not in the live production version. Usually we would need to depreciate but we should be ok for a removal here as this was for internal use on a prototype.
The removal includes:
- Deleting the activity stream functionality from the current user's GraphQL interface
- Removing event target types and filtering capabilities that categorized different kinds of activities (issues, merge requests, projects, etc.)
- Eliminating the underlying data structures that defined what types of objects could be targets of user events
- Removing the feature flag configuration that controlled this experimental functionality
- Cleaning up all associated documentation and test files
The change also includes some minor code reorganization in the event filtering system, moving some methods to private sections for better code organization. This appears to be a rollback of an experimental feature that was likely not performing as expected or was being replaced by a different approach to user activity tracking.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #558158 (closed)