-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
With unquoted TOML values, GroupByParamDate requires fully qualified date #11563
Comments
jmooring
changed the title
GroupByParamDate requires fully qualified time date
With unquoted TOML values, GroupByParamDate requires fully qualified date
Oct 13, 2023
jmooring
added a commit
to jmooring/hugo
that referenced
this issue
Nov 13, 2023
jmooring
added a commit
to jmooring/hugo
that referenced
this issue
Nov 16, 2023
jmooring
added a commit
to jmooring/hugo
that referenced
this issue
Nov 16, 2023
jmooring
added a commit
to jmooring/hugo
that referenced
this issue
Nov 17, 2023
bep
pushed a commit
that referenced
this issue
Nov 22, 2023
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The unexpected behavior is limited to unquoted TOML values.
GroupByParamDate "eventDate" "2006-01"
works fine with all of these:But pages with this parameter date format are not grouped:
GroupByDate
,GroupByExpiryDate
,GroupByLastmod
, andGroupByPublishDate
work fine any of the four date values.In that unquoted TOML dates are the best choice1 for custom date params, this seems like something we should fix.
Reproducible example:
Footnotes
With unquoted TOML dates you can do
time.Time
comparisons wit thewhere
function. ↩The text was updated successfully, but these errors were encountered: