What problem does this solve?
This is a follow-up to #1815, whose most important point (the silent ignorance of symlinks) has already been fixed.
Currently, index_repository does not follow directory symlinks or NTFS junctions when walking the repo tree. Files reachable only through such a reparse point are completely absent from the resulting graph. From the tool's perspective, a symlink-directory (and everything under it) simply doesn't exist. This makes it quite difficult to index a codebase that uses linked/shared source directories without physically duplicating or hard-linking files.
Proposed solution
Allow the indexing of symlinks (probably via opt-in, so it is the job of the user to ensure no circular paths occur).
Alternatives considered
No response
Confirmations
What problem does this solve?
This is a follow-up to #1815, whose most important point (the silent ignorance of symlinks) has already been fixed.
Currently,
index_repositorydoes not follow directory symlinks or NTFS junctions when walking the repo tree. Files reachable only through such a reparse point are completely absent from the resulting graph. From the tool's perspective, a symlink-directory (and everything under it) simply doesn't exist. This makes it quite difficult to index a codebase that uses linked/shared source directories without physically duplicating or hard-linking files.Proposed solution
Allow the indexing of symlinks (probably via opt-in, so it is the job of the user to ensure no circular paths occur).
Alternatives considered
No response
Confirmations