Link to another local markdown is not resolved using the explicit relative path from existing files

[racinmat]

What happened?

I have 3 files I created manually, and then opened containing folder in logseq.

file readme.md:

# this is readme

we have 2 other files
- [file name 1](file_name_1.md)
- [filename2](filename2.md)

file file_name_1.md

# File name 1

This is file 1

file filename2.md

# Filename 2

This is the file 2

Reproduce the Bug

Create manually above-mentioned files.
Open logseq and choose the directory containing them.
There, click All pages, click readme and then click the file name 1.

Expected Behavior

any other markdown viewer, or github.com, is able to link the file_name_1.md file to the link in readme.md, and if I click the link, it opens the correct file.
I expect the logseq to do the same.
Instead, logseq opens a new page, called file name 1

Screenshots

readme opened:

new page created:

the page I want to be opened by the link

Desktop Platform Information

Windows 10, build 19044, Logseq App version 0.6.7.0

Mobile Platform Information

No response

Additional Context

No response

[cnrpman]

Ref [[file_name_1]] should be able to navigate to your page.
There's no "local markdown" in Logseq. All pages in Logseq are flat. .md or .org in Logseq is only for the underling file storage, and should be insensible for user.

[kostyfisik]

I am thinking about the longevity of my notes again (as Dendron stopped being actively developed)... And being standard compliant seems to be a big thing.

I belive that the topic of local links should be extende to local relative links with #section support. They are not part of makdown spec (aka CommonMark), however, they can be considered to be standard de facto . Relative links are widely supported in many systems, e.g. in PKM's like Obsidian and Dendron, but also in Markdown publishing tools, e.g. ReadTheDocs for both backends (MkDoc and Sphinx), VitePress, Nuxt content, and many other. An important cases are GitHub (blog) and GitLab projects.

@cnrpman What do you thing about adding support of relative local links (including section links syntax) to the Logseq? As part of the core or maybe as a plugin?

[kostyfisik]

BTW, Logseq users and plugin providers also assume that it is working, e.g. see discussion

[cnrpman]

Yeah it will be a useful function. It's widely adopted by file-based note apps.

It's not on the radar yet. But code contribution is welcome.

Another reason is, Logseq is treating the graph directory "flat" - a page can be located with the file's basename only.
"Relative path" is not that compatible with this design.