feat: support dev.path & dev = true

[benlubas]

I'm pretty sure that this works. but rocks-dev.nvim doesn't seem to work if it's installed with rocks-git.nvim so I don't have a good way to test until it's published I don't think.

Is there a way to further isolate the tests? neovim globals seem to persist between tests so I had to explicitly unset it after each test for it to work.

---

• Pull request title has the appropriate conventional commit prefix.
• Tested
  • Tests have been added.
  • Tested manually. I am unable to test manually, the plugin doesn't seem to work when installed from git.
• Updated documentation.

[github-actions]

Review Checklist

Does this PR follow the Contribution Guidelines? Following is a partial checklist:

Proper conventional commit scoping:

• For example, fix(installer): some installer bugfix

• Pull request title has the appropriate conventional commit prefix.

If applicable:

• Tested
  • Tests have been added.
  • Tested manually (steps in PR description).
• Updated documentation.

[mrcjkb]

Thanks for the contribution 🙏 🚀

Looks mostly good to me. Just some minor suggestions.

[mrcjkb]

Is there a way to further isolate the tests? neovim globals seem to persist between tests so I had to explicitly unset it after each test for it to work.

I think this is only possible if you use GNU parallel or fd -x to run each test file in parallel. But then you need to make sure the environments are isolated.

[mrcjkb]

Tested manually. I am unable to test manually, the plugin doesn't seem to work when installed from git

Strange 🤔
Are you using rocks-git.nvim?
Anyways, the automated test looks good to me.

[mrcjkb]

One more request (sorry):

Could you please squash the commits?
Otherwise release-please will pick up your fix commit as a bug fix in the changelog.
I don't know why, but squashing with the GitHub UI doesn't seem to work so well with release-please.

[benlubas]

Done, also added a note about dir having priority over dev = true