[go: up one dir, main page]

Skip to content
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

page-title-format with "MMM" can break Jornals #11429

Open
1 of 2 tasks
carlinigraphy opened this issue Jul 20, 2024 · 0 comments
Open
1 of 2 tasks

page-title-format with "MMM" can break Jornals #11429

carlinigraphy opened this issue Jul 20, 2024 · 0 comments

Comments

@carlinigraphy
Copy link

Search first

  • I searched and no similar issues were found

What Happened?

Certain page-title-format dates seemingly break the Journal displaying.

My desired journal format is: yyyy/MMM/dd, EEEE. It should display as "2024/Jul/19, Friday". It's my preferred format, as it takes use of hierarchies to better index & find journal entries, as well as reading more legibly w/ month names.

The following work:

  • yyyy/MM/dd
  • yyyy MMM/dd

But surrounding the MMM format with either dashes or slashes breaks things:

  • yyyy-MMM-dd
  • yyyy/MMM-dd

There are no errors thrown in the console. To confirm, I used invalid date formats such as yyyy/MM/dddd, and observed errors in the console.

This also seems to be consistent with "MMM", "MMMM", "EEE", or other non-numeric formats.

Reproduce the Bug

I use Logseq desktop for Linux, but this is reproducible across MacOS, Linux, and the browser. The browser-based app can demonstrate a minimally reproducible issue:

  1. Go to: https://demo.logseq.com/#/
  2. Edit the global config.edn
  3. Set :journal/page-title-format "yyyy/MMM/dd"
  4. Re-index

Expected Behavior

Journal will be displayed with the desired format: yyyy/MMM/dd -> 2024/Jul/19.

Screenshots

No response

Desktop or Mobile Platform Information

Logseq Linux app 0.10.9
Logseq MacOS app 0.10.9
Chromium 126.0.6478.126 (running Logseq 0.10.9)

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

  • I'm willing to submit a PR (Thank you!)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant