Prefer message timestamp over the last-modified header for asset file dates#1321
Merged
Tyrrrz merged 2 commits intoDec 12, 2024
Merged
Conversation
Contributor
There was a problem hiding this comment.
Copilot reviewed 3 out of 3 changed files in this pull request and generated no suggestions.
Comments skipped due to low confidence (1)
DiscordChatExporter.Core/Exporting/ExportAssetDownloader.cs:54
- The indentation of the 'if (timestamp is null)' block is incorrect. It should be aligned with the rest of the code.
{
Tyrrrz
reviewed
Dec 1, 2024
last-modified header for asset file dates
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.
Fixes #1320.
With this PR, date-modified timestamp for attachments now prefers the timestamp of the message in which the attachment was originally shared on Discord:
Performing export of the same channel as originally shared in #1320:
Not sure if this is the best approach to implement this, but it seems to work well enough for my current use-case.