Hi, I am creating a business modeling tool based on logseq. I am using namespaces in a scenario similar to the one described here:
Here there are my understandings so far of data structures available on Logseq, feel free to comment and eventually correct me:
More than the “pages are collections of blocks” I like “pages are blocks with a name”.
We have indentation to create hierarchies between blocks.
Indentation of blocks can create hierarchies between pages too, the trick is using blocks containing only a reference to a page: - [[Parent]]
- [[Child]]
- [[Teddy]]
- Some text (eventually)
E…
So what are use cases for namespaces? The cases with huge overlap of childs names between different parents, for example:
Books’ chapters, lessons numbers:[[My New Book Title/Chapter 1]][[Another Book/Chapter 1]][[An Online Course/Lesson 1]][[An Online Course/Lesson 2]]
When I change the name of a page that is part of the namespace of other pages (children), it only updates the namespace for some of the children. You can see it in the following video:
Additional infnormation:
Here’s one of the pages that have not been updated (notice the hierarchy section):
I’ve tried re-indexing with no luck
Update: The problem seems to be related with this issue:
opened 06:02PM - 18 Sep 22 UTC
:type/enhancement
ux
hierarchy
filenames
page-rename
### What happened?
After I renamed my "algo" page to "Algo", the root namespa… ce, the namespace hierarchy is still showing the name "algo" for the child namespaces. Even I manually changed the file names and re-indexed but that didn't work out. I did manually change some of the notes name, but I was expecting that once I update the root namespace, all the sub-hierarchies (and wherever they are linked) should get automatically updated.
Here is what that inconsistency looks like:
Interestingly, the query {{namespace Algo}} is showing the right names of the namespaces when I hover-over the result of that namespace query but the default hierarchy block shown at the end doesn't have the updated name, this hovering over incosistency is shown below:
I am having hard time renaming stuff, [here is one more bug on the rename](https://github.com/logseq/logseq/issues/6764)
### Reproduce the Bug
1. Create a namespace hierarchy, with some levels to it (as my hierarchy shown above)
2. Rename the root note.
3. Go to the root note now.
4. (optional) Rename the "root" part in the file name of all the notes in local storage.
5. Go to the root note, and see the inconsistent hierarchy there.
### Expected Behavior
Once I rename the root, all the hierarchies and references to that should automatically take the root name. In more general terms, once I rename part of the namespace, that effect should be cascaded to all the sub-hierarchies.
### Screenshots
_No response_
### Desktop Platform Information
Windows 10 Version 10.0.19044 Build 19044
Logseq 0.8.7
### Mobile Platform Information
_No response_
### Additional Context
_No response_
Any idea of what might be happening? Thanks in advance,
