project file in /home/

[osaund]

Any nitpick ROOT_FILES/PROJECT_FILES within the parent directory cause the app to use this as the project directory and thus config files are created in the wrong location.

I had a pipfile in my home directory that was causing the issue.

2021-07-16 11:40:28.389 | DEBUG | nitpick.project:find_root:81 - Project files seen: {PosixPath('/home/me/Pipfile'), PosixPath('/home/me/Pipfile.lock')}

My project directory was then set to /home/me rather than the correct place and where nitpick was run from /home/me/project

Why do we climb the file tree? Why not just use the current dir and fail if nothing is found? Push it back to the user rather mainting the overhead of trying to "find" the root

[andreoliwa]

Thanks for filing this bug.

You read my mind somehow.
There is a card about this: https://github.com/andreoliwa/nitpick/projects/1#card-59976086

Yes, climbing is not the ideal behaviour, I will change it.

[1kyu]

But what about the default config file location like $HOME/.nitpick.toml and $HOME/.config/.nitpick.toml?

[andreoliwa]

But what about the default config file location like $HOME/.nitpick.toml and $HOME/.config/.nitpick.toml?

@1kyu this is an interesting idea, but it's not related to this bug.

I created a separate issue: #417
Take a look and check if it's what you originally thought; if not, drop a comment there.
Thanks!

[github-actions]

🎉 This issue has been resolved in version 0.30.0 🎉

The release is available on:

• v0.30.0
• GitHub release

Your semantic-release bot 📦🚀