Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Merging of pages doesn't work

オープン
#41 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
静か
技術スタック
clojure
領域
search

調査の方向性

番号付きの再現手順から始め、兄弟ブロックの場合とネストされたブロックの場合を比較してください。レポートにはソースファイルもテストのエントリーポイントもありません。関連する issue #8286 を確認してコンテキストを把握し、そのうえで A2 を A1 にマージするとリンクされた参照が2つ生成され、両方のブロック配置が一貫して更新されることを検証してください。

索引モデルが issue の本文から書いたものです。

説明

Search first
  • I searched and no similar issues were found
What Happened?

When a page is merged with another page, the resulting reference count is not updating correctly, unless the reference to the page to be merged is in the child node of the node containing the reference to the page to be merged with.
e.g. Merging #B with #A as follows, doesn't result in increased count of references to page #A
- #A
- #B
, but when #B is in a child node of #A ...
- #A
--- #B
.... .it works as expected.

Detailed description of the anomalies observed is provided in the "Reproduce the Bug" section.

Also, the symptoms I experienced are already described thoroughly in the following links:

  1. merging pages are incorrect #8286
  2. marging pages isn't working
Reproduce the Bug

1.Create 2 sibling blocks containing 2 different page references, e.g: "A1" and "A2" in them
- Block 1 #A1
- Block 2 #A2 ; ( to be merged with "A1")
2. Verify that both "A1" and "A2" have one linked reference each... and multiple unlinked ones.
3. Merge "A2" to "A1" ( by opening the "A2" page, renaming "A2" to "A1" and clicking "yes" on the resulting dialog box i..e "Page “A1” already exists, merge to it?")
4. Open "A1" page. There is '1 Linked Reference to "A1" listed where 2 are expected. Restarting #Logseq doesn't change that.

NOTE: if content of the parent block of blocks "Block 1..." and "Block 2..." is edited in some way, e.g. by adding space before "Create", the reference count in the "A1" page will update correctly.
Editing the content of "Block 2" also results in correct number of references.
Editing the content of "Block 1" doesn't affect the number of listed linked references. (???)

  1. ! When "Block 2" is a child of "Block 1", the inconsistencies described above don't occur.

The following markdown can be pasted into a Logseq page:

 -
-   1.Create 2  sibling blocks containing 2 different page references, e.g: "A1" and "A2"  in them
  logseq.order-list-type:: number
	- Block 1 #A1
	- Block 2 #A2  ; ( to be merged with "A1")
- Verify that both "A1" and "A2" have one linked reference each... and multiple unlinked ones.
  logseq.order-list-type:: number
- Merge "A2" to "A1" ( by opening the "A2" page, renaming "A2" to "A1"  and clicking "yes" on the resulting dialog box i..e "Page “A1” already exists, merge to it?")
  logseq.order-list-type:: number
- Open "A1" page. There is '1 Linked Reference to "A1" listed where 2 are expected. Restarting #Logseq doesn't change that.
  logseq.order-list-type:: number
  > NOTE: if content of the parent block of blocks "Block 1..." and "Block 2..." is edited in some way, e.g. by adding space before "Create", the reference count in the "A1" page will update correctly.  
Editing the content of "Block 2" also results in correct number of references.  
Editing the content of "Block 1" doesn't affect the number of listed linked references. (???)  
- ! When "Block 2" is a child of  "Block 1", the inconsistencies described above don't occur.
  logseq.order-list-type:: number
Expected Behavior

after merging pages, all of them should appear as linked references?

(the above paragraph is an excerpt from merging pages are incorrect #8286

Screenshots

No response

Desktop or Mobile Platform Information

App Version: 1.0.0
Git Revision: 680b371
Platform: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML like Gecko) LogseqOG/1.0.0 Chrome/140.0.7339.240 Electron/38.4.0 Safari/537.36
Language: en-US
Plugins: logseq-regex-linker (v2.0.1), logseq-plugin-hierarchy-tool (v1.2.0), logseq-block-calendar (v0.2.11), logseq-elysium (v0.1.1), logseq-plugin-automatic-url-title (v1.1.0), logseq-plugin-template-block-from-toolbar (v1.1.0), logseq-query-builder-plugin (0.81), logseq-todo-plugin (v1.22.0), logseq-journals-calendar (v0.11.0), logseq-dynamic-lookup (v1.4.0), logseq-lumalee (v0.2), logseq-bullet-threading (v1.1.4), logseq-flow-nord-theme (v0.10.41), logseq-page-tags-and-hierarchy (v2.25.2), logseq-datenlp-plugin (v4.7.3), logseq-get-youtube-captions (v1.3.0), logseq-inbox-telegram-plugin (v0.1.5), logseq-todo-master (v1.10.3), logseq-page-breadcrumb (v1.0.1), logseq-agenda (v3.13.1), logseq-hypothesis (v0.2.4), logseq-add-para-properties (v1.2.1), logseq-kanban-plugin (v3.8.1), logseq-tags (v0.1.2), logseq-graph-analysis (0.12.0), logseq-smartblocks (3.51), logseq-mark-map (v0.4.6)

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!)
主要言語
Clojure
スター
321
フォーク
60
PR マージ指標
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

logseq/og のほかの issue

logseq/og の issue をすべて見る

似ている issue

Clojure の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。