Skip to content

feat/auto-detect-cwd-as-default-path#16

Open
jara505 wants to merge 3 commits intoaikhe:masterfrom
jara505:feat/auto-detect-git-repo
Open

feat/auto-detect-cwd-as-default-path#16
jara505 wants to merge 3 commits intoaikhe:masterfrom
jara505:feat/auto-detect-git-repo

Conversation

@jara505
Copy link
Contributor

@jara505 jara505 commented Mar 16, 2026

Overview

Change the default behavior to auto-detect the current working directory instead of hardcoding ~/.config/nvim. This allows the plugin to work with any git repository without requiring manual path configuration. Still maintains backward compatibility for users who want to specify a custom path.

Key Changes

  • Update state.lua to default path to empty string
  • Modify setup() in init.lua to use vim.fn.getcwd() when path is empty
  • Update README documentation

Impact

  • lua/wrapped/state.lua - Default path configuration
  • lua/wrapped/init.lua - Auto-detection logic
  • README.md - Documentation update

jara505 added 3 commits March 15, 2026 17:41
Add keys configuration option to allow users to customize
dashboard keybindings (open, close, refresh, prev/next year).
Change default path from ~/.config/nvim to auto-detect the
current working directory, allowing the plugin to work with
any git repository without manual configuration.
@jara505
Copy link
Contributor Author

jara505 commented Mar 16, 2026

Hi!!!

I've been digging into the codebase today and submitted a few contributions to improve the tool.

If you’d like, I’d also be happy to help reviewing PRs or assist with code reviews for the project.

@aikhe aikhe self-assigned this Mar 17, 2026
@aikhe
Copy link
Owner

aikhe commented Mar 17, 2026

haloo @jara505

mb for taking this long to review the pr's :<

wrapped is currently only scoped for the user's neovim configuration (via :WrappedNvim), which is why that hardcoded path check is there:

if not state.config.path or state.config.path == "" then
  state.config.path = vim.fn.stdpath "config" --[[@as string]]
end

this ensures the plugin has a safe fallback to the user's config directory. this logic will definitely be great to revisit once :WrappedProject #12 is implemented though, as we'll need more dynamic path handling then.

Copy link
Owner

@aikhe aikhe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi!!!

I've been digging into the codebase today and submitted a few contributions to improve the tool.

If you’d like, I’d also be happy to help reviewing PRs or assist with code reviews for the project.

definitely!

i took a bit of break recently from my plugins, so it would great to have someone helping to build this plugin. feel free to suggest features (especially on #12), open new PRs, or help with reviews!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants