Skip to content

Add more control how file paths in output are formatted #1424

@Gintasz

Description

@Gintasz

Description

Currently file paths in output are relative to the analysis folder, e.g. if you do repomix . in project folder, and it has src/main.py, you'll see:
<file path="src/main.py">

Sometimes you have an extension of project's source code that's in a different folder from current working directory, e.g. ../core-library/. So then you can do repomix ../core-library/. E.g. this one has file src/core.py, and in output you'll see:
<file path="src/core.py">

Suggestion: add optional modes how these file paths should be formatted in the output. E.g. in this case it would be preferrable to instead have <file path="../core-library/src/core.py"> in the output, which is relative to the current working directory.

I'm trying an approach where if it's a smaller project, I ask agent to run repomix and get all project-related source code into context. But this pathing makes it forget that not all files are under the current working directory, so it wastes time searching for the file in current working directory, then realizes it's not there, and goes to the correct folder.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestneeds discussionIssues needing discussion and a decision to be made before action can be taken

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions