fix(#2094): fix the path resolving in windows

[guanghechen]

RC: The vim.fs.normalize will return a invalid filepath in windows like C:\xxx\yyy\zzz

The new avante.utils.path module is modeled after Node.js's node:path API. I've been using this code in my personal Neovim configuration for over a year, and it has proven to be quite reliable for cross-platform path resolution and relative path handling.

[guanghechen]

@yetone I have a confusion on the empty string path case, shouldn't it get . instead of ''? Since the normalize will always return . instead of

  it("should return empty string when no paths provided", function()
    local result = utils.join_paths()
    assert.equals("", result)
  end)

[yetone]

@yetone I have a confusion on the empty string path case, shouldn't it get . instead of ''? Since the normalize will always return . instead of

  it("should return empty string when no paths provided", function()
    local result = utils.join_paths()
    assert.equals("", result)
  end)

It feels like there is no standard answer to this question.

[guanghechen]

Yeah, but since there are already defined the behavior of the path.relative(empty string) to ., do you mind I change the test case to let the join_paths() return .?

[brewinski]

I think this might have introduced a bug when opening Avante with an empty buffer.

When I start Neovim and press aa, all of the files in the current directory are opened and I get the following error:

This is on MacOS 15. Anyone else running into this bug?

[guanghechen]

will check it soon

[guanghechen]

Hum, seems cannot repro it in my macos device

[guanghechen]

I think I find what the issue is — is your current buffer a directory (like the cwd)? I believe that when opening Avante from a directory buffer, it shouldn't be added to the selected files list. will try to draft a pr to fix it.

[guanghechen]

@brewinski can you try this fix?

#2254

[brewinski]

Thanks @guanghechen for looking into this so quickly. Yes, #2254 change fixed the problem for me. :)