FeedManager methods that accept activity as argument expect it to be of type Activity and not EnrichedActivity. On the other hand, the react-activity-feed components are working always with EnrichedActivity objects and that leads to type conflict when calling e.g. feed.onAddReaction inside the component. However these FeedManager methods could accept EnrichedActivity as well, without causing any issues executing the API calls. The proposed solution is to change the activity arg type to activity: Activity | EnrichedActivity. This should not lead to any breaking changes.
FeedManagermethods that acceptactivityas argument expect it to be of typeActivityand notEnrichedActivity. On the other hand, the react-activity-feed components are working always withEnrichedActivityobjects and that leads to type conflict when calling e.g.feed.onAddReactioninside the component. However theseFeedManagermethods could acceptEnrichedActivityas well, without causing any issues executing the API calls. The proposed solution is to change theactivityarg type toactivity: Activity | EnrichedActivity. This should not lead to any breaking changes.