bug: LspProgress change in recent neovim commits

[embe221ed]

Did you check docs and existing issues?

• I have read all the noice.nvim docs
• I have searched the existing issues of noice.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

NVIM v0.10.0-dev-3097+g064f3e42e

Operating system/version

MacOS

Describe the bug

neovim/neovim@e14e750

Steps To Reproduce

open *.lua file with lsp progress feature enabled

Expected Behavior

no errors

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/noice.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

[embe221ed]

diff --git a/lua/noice/lsp/progress.lua b/lua/noice/lsp/progress.lua
index 257dc6a..11689cc 100644
--- a/lua/noice/lsp/progress.lua
+++ b/lua/noice/lsp/progress.lua
@@ -16,7 +16,7 @@ M._running = false
 ---@param data {client_id: integer, result: lsp.ProgressParams}
 function M.progress(data)
   local client_id = data.client_id
-  local result = data.result
+  local result = data.params
   local id = client_id .. "." .. result.token

   local message = M._progress[id]

[embe221ed]

created this as a heads up, didn't want to create a PR as I think this is not an issue for now, but will be in the future once this commit is included in the release

[ulisses-cruz]

This is already an issue for me

[carlosala]

Yep, it's already on nightly.

[gldtn]

This is already an issue for me

Same, hoping the PR(#785) gets accepted soon 😁