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.
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
Use recent_private_conversations on PMs screen, when available #4104
Use recent_private_conversations on PMs screen, when available #4104
Changes from all commits
df57102
deac44e
e665047
7c70e3d
ae35faa
7529da2
c95cd36
fcc3b53
beebd5e
3441017
d36e1c0
eb119f5
c753f0a
ae7db07
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This catches my eye because
MessagesState
may switch from an object-as-map to a Map or Immutable.Map soon, and I'd like to rely on the type-checker to find places we need to update.When I remove the fixme, one thing I notice is there are actually two errors here -- and one of them isn't related to that Flow bug, I think, but comes from the fact that (a)
Message
is an inexact type, but (b)MessagesState
uses$Exact<Message>
. That contrast seems odd and I don't recall why we have it.I'd feel better if this were explicit about what kind of type difference it's meant to launder. If e.g. this line were to spell out what the
MessagesState
type is -- which will look very similar to the type onstate
just above, so the reader can compare to see what's being fudged -- then I think that'd do it. Then Flow would check that that type indeed can be used asMessagesState
, so when the latter changes incompatibly it'll give an error here.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.
This bit was in Isham's version, but I just noticed it: do you see a reason this type should get dropped?