Repository navigation
feat(channels): filter channel list by keyKnown - #197
Merged
Merged
Conversation
Also seed the cursor integration test with MeshMapper membership; it still used channel_iatas after channel lists moved to region scoping.
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.
Adds an optional
keyKnown=true|falsequery param toGET /api/v1/channels. The filter runs in both list queries beforeLIMIT, so cursors andhasMorereflect the filtered set. NULLkey_knowncounts as false, matchingChannelSummary.KeyKnown. Any other value returns 400.The web Channels list will load all decryptable channels first, then page the rest behind "Load other channels".
Also fixes the
TestChannelCursorPostgresseed, which still usedchannel_iatasafter channel lists moved to MeshMapper/config scoping.