feat(community-feed): add ComposerPrompt and auto-enable Blacksky-Only on the Community tab#115
Open
jalcine wants to merge 2 commits into
Open
Conversation
Author
|
Hm, will fix lints in a moment |
jalcine
force-pushed
the
feat/community-tab-auto-blacksky-only
branch
from
July 16, 2026 17:54
75ce9bb to
24d42ce
Compare
jalcine
force-pushed
the
feat/community-tab-auto-blacksky-only
branch
from
July 16, 2026 17:55
24d42ce to
150f933
Compare
Three pre-existing issues that block the pre-commit hook: - fetchNextPage() not awaited inside onEndReached (floating promise) - async onRefresh bound directly to the FlatList onRefresh prop (misused-promise — the prop expects a void-returning function) - imports not sorted alphabetically by directory then name (the simple-import-sort/imports rule) Mark the promise-returning calls with void and wrap onRefresh in a handleRefresh helper so the FlatList prop gets a void-returning function. Reorder the imports to satisfy the sort rule. No behavior change.
…y on the Community tab Surface the inline 'What's happening?' composer prompt above the Community feed, matching the Following feed's affordance. Tapping the prompt (or the existing FAB) opens the standard composer. When the composer is opened while the Community tab is the active selected feed, the Blacksky-Only toggle now defaults to ON so the composer matches the tab context. The toggle is per-instance on the Community tab — manually flipping it off there does NOT update the sticky blackskyOnlyDefault preference, so the next composer on the Community tab will default back to ON. This complements the existing forced-on path (community-post reply or quote target) and the user's sticky preference. Precedence: forced > community-tab context > sticky default.
Author
|
@rudyfraser I rebased this and shrunk the commits but looks like jobs aren't running |
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
1 participant
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.
The Community tab had only the floating compose button — the Following feed's inline "What's popping?" composer prompt was missing, and the composer never reflected the tab context. Surface the prompt as the community feed's list header and have the composer default the Blacksky-Only toggle ON when opened while the Community tab is active. The toggle stays per-instance there: flipping it off doesn't touch the sticky
blackskyOnlyDefaultpreference, so users get community-only on the Community tab without affecting their other posts.