-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Add global setting how timestamps should be rendered #28657
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
Changes from 1 commit
ecfd154
b3d60f7
bbe69c3
0504a8c
5819397
b00611a
12b3b49
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -1244,6 +1244,9 @@ LEVEL = Info | |||||
| ;; Change the sort type of the explore pages. | ||||||
| ;; Default is "recentupdate", but you also have "alphabetically", "reverselastlogin", "newest", "oldest". | ||||||
| ;EXPLORE_PAGING_DEFAULT_SORT = recentupdate | ||||||
| ;; | ||||||
| ;; Whether to prefer all timestamps to be rendered as absolute. Setting this to false means some timestamps would render as relative. | ||||||
| ;PREFER_ABSOLUTE_TIMESTAMPS = false | ||||||
|
||||||
| ;PREFER_ABSOLUTE_TIMESTAMPS = false | |
| ;TIMESTAMP_FORMAT = relative |
with relative,absolute being the possible options (for now)
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.
I don't think other options exist
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.
I can think of a few at the top of my head: relative_v2, relative_legacy, absolute_v2, absolute_legacy, both, …
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.
If relative is set here, some timestamps still render as absolute though (e.g. joined on date in profile page)
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.
Yeah, but those are either intended or a bug.
Either way, to me it makes sense despite some minor exceptions.
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.
Okay, if you add a comment why relative does not yet exist.
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.
My current description is:
PREFERRED_TIMESTAMP_TENSE: mixed: The tense all timestamps should be rendered as. Possible values areabsolutetime (i.e. 1970-01-01, 11:59) ormixedwhich means some timestamps would render as relative (i.e. 2 days ago).
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.
Today some of our timestamps are absolute and some are relative. I don't know why.
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.
some most
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.
Done 0504a8c
Uh oh!
There was an error while loading. Please reload this page.