Added timestamps back to compact message cards #1267
Merged
Conversation
This file contains 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
|
I think we may have removed them on purpose because of some reasoning around not getting updates quickly enough and that users shouldn't ignore old content just because it is old and therefore less valid supposedly. I may be misremembering. That being said I support re-enabling them whether it happened on purpose or by accident. |
|
Matt informed me that this isn't ready as it breaks some things so I am converting it to draft to avoid confusion. |
|
I thought this broke the thread view because the reply box isn't displayed by default. But I realize that it just works differently now: you have to tap the reply button to show the reply view. So this didn't actually break anything and it's ready for review. |
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.
Not sure when these went away, but I don't think it was intentional. I also fixed an Xcode 14.2 bug.