Fix gig account filtering and content link parsing - #557
Merged
ralyodio merged 3 commits intoSep 12, 2026
Merged
Conversation
ralyodio
marked this pull request as ready for review
September 12, 2026 15:42
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
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.
Three small correctness fixes, each in its own commit:
alice@example.comcurrently becomes a profile link toexample; it now remains text. Real mentions preserve their surrounding text and displayed case./pull/12abcand/pull/12.5currently pass link validation even though the PR-coordinate parser rejects them. Genuine PR URLs, subpaths and search/list URLs remain supported.posterrelation alias with an inner join when account_type is supplied. Without the inner join, filtering the embedded profile does not exclude nonmatching gigs. Unfiltered searches retain their left join.Validation:
tsc --noEmit: passes.Prepared by an AI coding assistant with the account owner's authorization. No live database/customer data used, no production changes. The earlier account-filter patch is included as an open-source contribution; this PR is not an invoice or assertion of an agreed bounty.