-
-
Notifications
You must be signed in to change notification settings - Fork 673
stream IDs: sharing, links, tests #5183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
d56d46d
message tests: Use a whole stream object instead of a name
gnprice 9babb6a
narrow tests: Use whole stream objects rather than bare names
gnprice dc33793
internal-links tests: Use whole stream objects rather than bare names
gnprice 792ee46
drafts tests: Well-type draftsSelectors-test.js
gnprice 76504ea
drafts tests: Use whole stream objects rather than bare names
gnprice 5c5fa15
sharing [nfc]: Cut never-used selector prop `subscriptions`
gnprice 19c2ef3
sharing: Fix a race on sending vs. changing the destination
gnprice 629fb2d
sharing [nfc]: Say streamName for a stream name, not "stream"
gnprice 1b547b4
sharing: Track a stream ID, as well as stream name
gnprice d682322
autocomplete [nfc]: Accept a null narrow in TopicAutocomplete
gnprice 8846f56
sharing [nfc]: Construct stream/topic narrows only for real streams
gnprice 9d05bba
webview html: Get stream name from stream, rather than message
gnprice eb60b45
webview html [nfc]: Dedupe a bit more logic within stream case
gnprice 62fb218
internal links: Reject unrecognized streams
gnprice 7627a1e
internal links [nfc]: Parse the stream ID, too
gnprice File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the proposed change doesn't add a ton of complexity, but also: in the first place, should the UI allow changing the message's destination while a send request is in progress? I think disallowing that is better than allowing it.
I can see wanting to change it after a request has started—but only if the request has failed or we've timed out on it, we've notified the user, and we want to let the user initiate a retry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, disallowing that in the UI would be quite reasonable.
Even then, I think it'd be cleaner for these callbacks to get
sendTofrom their caller (as they do with this change), rather than from the component's props (as they do before). That way the fact that this code all agrees on what conversation it's referring to is something that's straightforward to see locally -- the information gets read once and then passed around -- rather than have to wonder if there might be a way for it to get mutated between the different times we read it off the props.