How to make sense of large code bases in Logseq?

Questions & Help
1

I was wondering whether anyone has attempted to understand code bases in Logseq?

Is it possible to “mirror” some github repo and navigate and explore it in Logseq without having to copy paste code?

I think that code should be stored as structured data in a database and not unstructured data in files and folders.

Currently, I’m using fuzzyfinder and some extensions as a workaround, which allows me to search for some string. It is convenient because I don’t have to remember the file name and in which file or directory I put that function or variable.

2
  • Logseq doesn’t read arbitrary databases.
  • Searching throughout codebases is usually done with the help of some modern IDE.
  • In well-structured code:
    • all functions have a very specific place where they rightly belong to
    • all variables are local and their name is irrelevant outside the local scope
1 Like