get_node_text() behaves differently between buffer and string sources on EOL char

[cshuaimin]

Problem

If a treesitter node range's end_col is 0, vim.treesitter.get_node_text() will not return the trailing new line char for buffer source.

Steps to reproduce

test.lua:

local ts = vim.treesitter

local query = ts.query.parse("python", "(string_content) @s")

local function dbg(root, source)
  for _, nodes in query:iter_matches(root, source, 0, -1) do
    local node = nodes[#nodes]
    print("Range =", vim.inspect({ node:range() }))
    print("Text = |" .. ts.get_node_text(node, source) .. "|")
  end
end

local source = [[
"""test
"""
]]

print("====== string")
local root = ts.get_string_parser(source, "python"):parse()[1]:root()
dbg(root, source)

print("====== buffer")
local buf = vim.api.nvim_create_buf(true, true)
vim.api.nvim_buf_set_lines(buf, 0, -1, true, vim.split(source, "\n", { plain = true }))
root = ts.get_parser(buf, "python"):parse()[1]:root()
dbg(root, buf)

> nvim -l test.lua 
====== string
Range = { 0, 3, 1, 0 }
Text = |test
|
====== buffer
Range = { 0, 3, 1, 0 }
Text = |test|

Node ranges are same, but the result of get_node_text() is different.

Expected behavior

get_node_text() on buffers returns the trailing newline char, or does not return newline char on string sources, to make it consistent.

Neovim version (nvim -v)

NVIM v0.9.5 & NVIM v0.10.0-dev-d3fa88b

Vim (not Nvim) behaves the same?

no

Operating system/version

Linux

Terminal name/version

kitty 0.34.1

$TERM environment variable

xterm-kitty

Installation

nixpkgs