Fix empty top-level ActivityFeed component file - #997
Merged
RUKAYAT-CODER merged 2 commits intoJul 25, 2026
Conversation
|
@Meet-hybrid Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Thank you for contributing to the project. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The file src/components/ActivityFeed.tsx was effectively empty (containing only a blank line with no export). As a result, any import of this top-level component resolved to undefined and caused runtime errors when attempting to render.
This PR addresses the issue by:
Removing the unused/empty ActivityFeed.tsx file.
Updating imports to reference the existing social/ActivityFeed component instead.
Ensuring that all references to ActivityFeed resolve to a valid implementation.
Impact
Prevents runtime errors caused by undefined component imports.
Clarifies the source of the ActivityFeed component, reducing confusion for future contributors.
Improves overall codebase consistency by eliminating a misleading placeholder file.
Testing
Verified that all imports of ActivityFeed now resolve correctly.
Confirmed that the social feed renders without errors in the UI.
Closes #988