You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
.
The text was updated successfully, but these errors were encountered:
FeedManager
methods that acceptactivity
as argument expect it to be of typeActivity
and notEnrichedActivity
. On the other hand, the react-activity-feed components are working always withEnrichedActivity
objects and that leads to type conflict when calling e.g.feed.onAddReaction
inside the component. However theseFeedManager
methods could acceptEnrichedActivity
as well, without causing any issues executing the API calls. The proposed solution is to change theactivity
arg type toactivity: Activity | EnrichedActivity
. This should not lead to any breaking changes..
The text was updated successfully, but these errors were encountered: