Path:normalize appears to be reducing paths to their relative (without cwd) value

Open
#387 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua
Domain
tooling

Research direction

Start by locating the implementation of Path:normalize in plenary.nvim and reproduce the Lua example from the issue. Compare the returned value for the absolute path with the documented or intended meaning of the normalize argument. Done means the expected behavior is established and the issue is either clarified or the behavior is corrected with appropriate coverage.

Written by the indexing model from the issue text.

Description

This may not be a bug, but it does seem incorrect. If you provide an absolute path (as a string) to Path:normalize, you will receive the file/dir name itself and nothing else. I am not entirely sure the reasoning for this (The code for this function is easy enough but I assume this is being done for a reason).

An example of this is as follows

print(require("plenary.path"):new("/tmp/testing.py"):normalize("/tmp"))

This will print out
testing.py, when it I would assume it would print out /tmp/testing.py. Is this just a misunderstanding on my part?

Dominant language
Lua
Stars
3.5k
Forks
340
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nvim-lua/plenary.nvim

All issues in nvim-lua/plenary.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.