GithubMirrors/logseq
Watch
1
0
Fork
You've already forked logseq
 0
mirror of https://github.com/logseq/logseq.git synced 2026-10-06 09:31:02 +00:00
Code Issues Projects Releases Packages Wiki Activity
A privacy-first, open-source platform for knowledge management and collaboration. Download link: http://github.com/logseq/logseq/releases. roadmap: https://logseq.io/p/NX4mc_ggEV https://logseq.com
25,845 commits 319 branches 200 tags 509 MiB
  • Clojure 71%
  • OCaml 10.4%
  • JavaScript 8%
  • CSS 3.7%
  • Swift 1.5%
  • Other 5.3%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Tienson Qin 22a29b30de
 fix: resolve uuid refs in search results, breadcrumbs, and nested page refs (#13580) 
* fix: resolve uuid refs in search result titles

94ea551ec4 rewrote block-ref-id->title with (filter map? frontier),
but datascript entities are not map?, so recur-replace-uuid-in-block-title
silently stopped resolving refs for entity inputs (search index, search
results, breadcrumbs, export). ((uuid)) refs were additionally never
matched by the id-ref patterns or kept in :block/refs.

- accept entities as well as maps when collecting ref titles
- match ((uuid)) refs and replace them with the referenced title
- include ((uuid)) in get-matched-ids so :block/refs stays complete
- resolve ((uuid)) targets directly from the title instead of relying
  on :block/refs
- resolve search result titles in the worker through the entity, since
  pulled result maps lack :block/refs

* fix: resolve title id refs without :block/refs and rebuild index

* refactor: drop (()) support; node refs resolve via [[uuid]] only

Block and page are both nodes in db graphs and node refs uniformly use
[[uuid]], so (()) handling is removed from title resolution,
get-matched-ids, and search. Search now only re-resolves ref titles when
the title matches [[uuid]].

* fix: resolve nested uuid refs in breadcrumb titles

Breadcrumbs showed raw [[uuid]] for title refs that are not in :block/refs,
e.g. [[<foo-uuid>]] nested inside a page-ref name ([[[[foo]] bar]] nested).

- worker :block-breadcrumb ref-titles now also resolves every [[uuid]] found
  in ancestor titles via d/entity, transitively through ref titles, so the
  payload covers nested id refs (and watches those entities).
- with-breadcrumb-ref-titles appends shallow refs for ref-titles uuids that
  are missing from :block/refs.
- page breadcrumb segments resolve [[uuid]] in :block/title like block
  segments already did.

* fix: resolve nested uuid refs in breadcrumbs and page refs

The :block.temp/breadcrumb fast path dropped the worker-computed
:ref-titles, so nested uuid refs (e.g. [[<uuid>]] inside a page-ref
name) stayed raw in the header, page, sidebar, and search-result
breadcrumbs. Plumb :block.temp/breadcrumb-ref-titles alongside the
ancestors at every producer and read it back in breadcrumb.

Nested page refs like [[[[foo]] bar]] nested rendered the raw
stored name [[<uuid>]] bar because nested-link printed :block/name
directly. Look up the page by name via [:page-identity] and render
the resolved page title, falling back to the previous behavior for
missing pages.

Move breadcrumb-ref-titles into frontend.worker.handler.block-breadcrumb
so search results can attach :block.temp/breadcrumb-ref-titles too.

* test: expect :block.temp/breadcrumb-ref-titles in first-paint page map

* fix: resolve uuids nested inside breadcrumb ref titles
2026-10-03 22:57:34 +08:00
.agents/skills fix: resolve uuid refs in search results, breadcrumbs, and nested page refs (#13580) 2026-10-03 22:57:34 +08:00
.carve chore: prune carve ignore list 2026-09-08 15:40:23 +08:00
.claude enhance(dev): enable claude to read project skills 2026-05-16 17:32:49 -04:00
.clj-kondo refactor: migrate frontend state to rfx 2026-06-03 13:07:58 +08:00
.github fastlane tweaks 2026-10-03 19:28:15 +08:00
.lsp deprecated block-ref (#12627) 2026-05-14 13:21:22 +08:00
.spec-dev-tool/guides perf(views): speed up db table scrolling and clipped cells (#13226) 2026-09-16 21:04:11 +08:00
android chore: bump version to 2.0.2 2026-10-02 22:29:34 +08:00
assets fix(mobile): add splash screen pic for dark theme 2025-08-16 21:07:23 +08:00
bin chore: update logseq-i18n-lint binaries to 8b4f9304ecff 2026-05-08 10:27:09 +00:00
cli chore(cli): point opam pins at logseq org forks on main 2026-09-24 05:06:59 -07:00
cli-e2e fix(cli): tolerate workers exiting mid-health-check during retirement (#13413) 2026-09-25 00:26:48 +08:00
clj-e2e fix: resolve uuid refs in search results, breadcrumbs, and nested page refs (#13580) 2026-10-03 22:57:34 +08:00
deps fix: resolve uuid refs in search results, breadcrumbs, and nested page refs (#13580) 2026-10-03 22:57:34 +08:00
dist 036-db-worker-node-ncc-bundling 2026-03-12 15:12:33 +08:00
docs enhance(cli): document Markdown block input 2026-09-24 17:58:54 +08:00
externs fix(mobile): can't copy to clipboard 2025-08-20 03:35:00 +08:00
fastlane/metadata/android/en-US fix: add icon for fastlane metadata 2024-06-23 22:23:10 +08:00
icons Update splash screen 2025-07-10 16:28:05 +08:00
ios fastlane tweaks 2026-10-03 19:28:15 +08:00
libs fix: store plugin integer number properties as values (#13488) 2026-09-30 19:27:13 +08:00
prompts add logseq-i18n skill and polish docs 2026-04-15 22:14:06 +08:00
public refactor: replace Rum with HSX (#12748) 2026-06-02 08:52:37 +08:00
resources chore: bump version to 2.0.2 2026-10-02 22:29:34 +08:00
scripts fix: isolate persistence runtime unit tests (#13533) 2026-09-30 22:49:22 +08:00
sidecar chore: remove embedding progress log 2026-06-06 22:10:11 +08:00
src fix: resolve uuid refs in search results, breadcrumbs, and nested page refs (#13580) 2026-10-03 22:57:34 +08:00
.cljfmt.edn Merge branch 'master' into feat/hnswlib+transformer-js 2025-07-11 18:15:33 +08:00
.editorconfig Migrate from yarn to pnpm (#12529) 2026-04-24 23:40:25 +08:00
.gitattributes Fix issues related to importing file to db (#12353) 2026-01-30 17:36:12 +08:00
.gitignore fastlane tweaks 2026-10-03 19:28:15 +08:00
.i18n-lint.toml refactor: complete incremental block reactivity 2026-07-21 21:19:23 +08:00
.npmrc Migrate from yarn to pnpm (#12529) 2026-04-24 23:40:25 +08:00
.prettierrc.js Fix issues related to importing file to db (#12353) 2026-01-30 17:36:12 +08:00
.projectile fix: :block/name shouldn't be updated for custom date formatter 2026-04-29 16:44:22 +08:00
.stylelintrc.json refactor: add stylelint processor 2020-12-07 12:37:20 +08:00
AGENTS.md enhance: simplify agent-guide docs 2026-08-24 15:14:12 +08:00
bb.edn chore: remove old cli (#12739) 2026-05-28 20:16:13 +08:00
capacitor.config.ts fix(android): respect status bar safe area 2026-08-26 02:51:32 -07:00
CODE_OF_CONDUCT.md Minor typo fixes and grammar improvements 2024-01-30 16:16:40 -05:00
CODEBASE_OVERVIEW.md refactor: migrate to base ui 2026-06-02 15:57:54 +08:00
CONTRIBUTING.md fix: point issues to db-test repo 2026-08-18 00:18:10 +08:00
deps.edn chore: bump hsx 2026-06-10 18:15:56 +08:00
Dockerfile Migrate from yarn to pnpm (#12529) 2026-04-24 23:40:25 +08:00
externs.js fix(pdf): add extern hints for pdfjs apis 2025-12-15 18:05:32 +08:00
gulpfile.js chore: cleanup packages/ui from gulpfile 2026-08-12 13:21:36 +08:00
LICENSE.md fix(license): add exceptions for epl libraries 2020-11-03 23:46:52 +08:00
package.json feat(test): build db-worker-node for tests 2026-09-16 21:23:46 +08:00
pnpm-lock.yaml fix(graph): coordinate deletion with worker shutdown 2026-09-16 21:23:43 +08:00
pnpm-workspace.yaml fix: support pnpm 11 installs 2026-07-01 04:24:14 +08:00
postcss.config.js fix: stabilize worker-backed editor rendering 2026-07-23 15:15:47 +08:00
README.md Update web app to https://app.logseq.com 2026-07-15 17:20:59 +08:00
shadow-cljs.edn fix: configure mobile HTTPS dev server 2026-08-31 21:59:00 +08:00
tailwind.all.css fix: stabilize popup interactions 2026-06-05 09:58:52 +08:00
tailwind.config.js refactor: migrate to base ui 2026-06-02 15:57:54 +08:00
tailwind.mobile.css fix: ios mobile fonts 2026-06-11 12:31:15 +08:00
typos.toml Merge branch 'master' into refactor/state 2026-06-19 09:44:43 +08:00
webpack.config.js remove vector embeddings 2026-04-02 18:51:29 +08:00

README.md

Logseq

A privacy-first, open-source platform for knowledge management and collaboration



Download Logseq

forum chat on Discord follow on Twitter

latest release version

Table of Contents

🚀 Database Version

The Database version (DB version) of Logseq introduces DB graphs. See this page to get an overview of the main features for DB graphs. If you are an existing user, see changes with the DB version. The DB version has its own new mobile app (on iOS, with Android coming soon)! To participate in the mobile app alpha, please complete this brief form. The DB version also has a new sync approach, RTC (Real Time Collaboration)! You can use it to sync graphs between multiple devices or collaborate with others. To participate in the RTC alpha, please fill out this form.

The DB version is in beta status while the new mobile app and RTC is in alpha. This means that data loss is possible so we recommend automated backups or regular SQLite DB backups. We recommend you create a dedicated test graph and choose one project that’s not crucial for you.

To get started with the DB version:

  • To try the latest web version, go to https://app.logseq.com/.
  • To try the latest desktop version, go to https://github.com/logseq/logseq/releases/tag/nightly and download the artifact for your operating system.
  • To try the latest by building from the source code
    • Use test/db for stable releases. Fewer bugs and slower updates. Update frequency: days or weeks.
    • Use master for the latest updates as they are developed. Expect more bugs and faster changes. Update frequency: hours or days.
  • To report bugs, please file them at https://github.com/logseq/db-test/issues.
  • For feature or enhancement requests, please file them on Discord on the #db-feedback channel.
  • For discussions:
    • General ==> see the #db-chat channel in Discord.
    • Sync and RTC ==> see the #sync-test channel in Discord.
    • Mobile ==> see the #mobile-test channel in Discord.

🤔 Why Logseq?

Logseq is a knowledge management and collaboration platform. It focuses on privacy, longevity, and user control. Logseq offers a range of powerful tools for knowledge management, collaboration, PDF annotation, and task management with support for multiple file formats, including Markdown and Org-mode, and various features for organizing and structuring your notes.

In addition to its core features, Logseq has a growing ecosystem of plugins and themes that enable a wide range of workflows and customization options. Mobile apps are also available, providing access to most of the features of the desktop application. Whether you're a student, a professional, or anyone who values a clear and organized approach to managing your ideas and notes, Logseq is an excellent choice for anyone looking to improve their productivity and streamline their workflow.

logseq-demo

Download Logseq

👀 How can I use it?

To start using Logseq, follow these simple steps:

  1. Download the latest version of Logseq
  2. Install Logseq on your device and launch the application
  3. Start writing ✍️

That's it! You can now enjoy the benefits of using Logseq to streamline your workflow, manage your projects, and stay on top of your goals. Have fun! 🎉

Linux users: Use the automated installer script for the best experience:

# Download and run the installer
curl -fsSL https://raw.githubusercontent.com/logseq/logseq/master/scripts/install-linux.sh | bash

# Or install a specific version
curl -fsSL https://raw.githubusercontent.com/logseq/logseq/master/scripts/install-linux.sh | bash -s -- 0.10.14

# For user-specific installation (no root required)
curl -fsSL https://raw.githubusercontent.com/logseq/logseq/master/scripts/install-linux.sh | bash -s -- --user

📚 Learn more

🫶 Support Logseq Development

If you find Logseq useful and want to help us keep the project growing, please consider supporting our contributors on Open Collective. Your support shows our contributors that their efforts are appreciated and motivates them to continue their excellent work. Every contribution, no matter how small, helps us keep improving Logseq.

💡 Feature requests

We value your input on improving Logseq and making it more useful for you. If you have any ideas or feature requests, please share them in the Logseq Forum: Feature Requests section.

Your feedback helps us understand our users' needs and prioritize the features that matter most to you. We appreciate your time and effort in sharing your thoughts with us.

We appreciate your support, and we look forward to hearing your ideas!

🔌 Plugin API

Logseq provides a plugin API that enables developers to create custom plugins and extend the functionality of Logseq. The plugin API documentation is available at plugins-doc.logseq.com, where you can find everything needed to get started with plugin development.

We value your feedback and suggestions on how to improve our documentation. Please do not hesitate to contact us with any comments or questions. Your input helps us to provide a better experience for our users and developers.

Thank you for using Logseq, and we look forward to seeing what you create with our plugin API!

🌟 Contributing to Logseq

To start contributing to Logseq, please read CONTRIBUTING.md. There are ways to contribute with code and without code. We welcome all contributions, big or small, and we appreciate your time and effort in helping us improve Logseq. We look forward to your contributions 🚀

🛠️ Setting Up a Development Environment

If you want to set up a development environment for the Logseq web or desktop app, please refer to the Develop Logseq guide for macOS/Linux users and the Develop Logseq on Windows guide for Windows users.

In addition to these guides, you can also find other helpful resources in the docs/ folder, such as the Guide for Contributing to Translations, the Docker Web App Guide and the mobile development guide

🧰 Logseq CLI (Node)

Logseq CLI documentation is maintained in docs/cli/logseq-cli.md.

✨ Inspiration

Logseq is inspired by several unique tools and projects, including Roam Research, Org Mode, TiddlyWiki, Workflowy, and Cuekeeper.

We owe a huge debt of gratitude to the developers and creators of these projects, and we hope that Logseq can continue to build on their innovative ideas and make them accessible to a broader audience.

Thank you to all those who inspire us, and we look forward to seeing what the Logseq community will create with this tool!

Logseq is also made possible by the following projects:

  • Clojure & ClojureScript - A dynamic, functional, general-purpose programming language
  • DataScript - An immutable database and Datalog query-engine for Clojure, ClojureScript and JS
  • OCaml & Angstrom, for the document parser mldoc
  • isomorphic-git - A pure JavaScript implementation of Git for NodeJS and web browsers
  • SCI - A Small Clojure Interpreter

🙏 Thank You

We want to express our sincere gratitude to our Open Collective sponsors, backers, and contributors. Your support and contributions allow us to continue developing and improving Logseq. Thank you for being a part of our community and helping us make Logseq the best it can be!

💎 Sponsors

[Become a sponsor]

🌟 Contributors

Logseq - Your joyful, private digital garden | Product Hunt