fix(date): parse RFC 2822 and RFC 3339 date strings in --date flag#1163
Open
fix(date): parse RFC 2822 and RFC 3339 date strings in --date flag#1163
Conversation
Closes #1156 — `date --date="Mon, 06 Apr 2026 12:00:00 +0000"` now correctly parses RFC 2822 date strings instead of returning empty output. Also adds RFC 3339 parsing support.
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.
Summary
DateTime::parse_from_rfc2822) toparse_base_date()sodate --date="Mon, 06 Apr 2026 12:00:00 +0000"worksDateTime::parse_from_rfc3339) for timezone-aware ISO stringsWhy
date +"%B %d, %Y" --date="Mon, 06 Apr 2026 12:00:00 +0000"returned empty output becauseparse_base_datedidn't recognize RFC 2822 format. This broke bashblog's timestamp formatting.Tests
date_rfc2822_input,date_rfc2822_input_epochCloses #1156