How do I iterate over the Sections dynamically?

[PhilippFeO]

I want to iterate over the values jump_to_view() (and show_view()) can consume:

---@param view "breakpoints" | "exceptions" | "watches" | "repl" | "threads" | "console" | "scopes" | "sessions" | string
require("dap-view").jump_to_view(view)

Where do I find them in the codebase? I probably start with require 'dap-view' but then? I searched the codebase but all I can find are the listings in the docstring.

Since I am not the most proliferate lua-nvim-wizard out there, so I don't know, if my goal is feasible or not.

[igorlfs]

Hello,

I want to iterate over the values jump_to_view() can consume:

This sounds like an XY problem. What exactly is your end goal?

[PhilippFeO]

Initially, I thought of dynamically creating keymaps to jump to each section, fi. <Leader>j? where ? encodes a section corresponding letter.

In practice, I don't need all of these keymaps, fi. I rarely have to jump to Breakpoints. So, it's more of getting better at Lua/plugins/neovim. More or less, low priority, rather curiosity.

[igorlfs]

I want to iterate over the values jump_to_view() (and show_view()) can consume

These functions only allow you to jump to the sections (views) you have configured. If you're using the default configuration, they are

{ "watches", "scopes", "exceptions", "breakpoints", "threads", "repl" }

Else, you're setting the winbar.sections somewhere, which allows you to:

local my_sections = { "watches", "scopes", "threads", "console" }
local binds = {"w", "s", "t", "c"}

require"dap-view".setup({
    winbar = {
        sections = my_sections
    }
})

for i, v in ipairs(my_sections) do
    vim.keymap.set("n", "<leader>j" .. binds[i], function ()
        require"dap-view".jump_to_view(v)
    end, {desc = "DAP View - Jump to " .. v})
end

Where do I find them in the codebase? I probably start with require 'dap-view' but then? I searched the codebase but all I can find are the listings in the docstring

Grepping for jump_to_view is a good start :p
If you take a look at the source, you'll notice that the function uses a special type annotation from LuaLS, because the parameter is an alias. Using an alias for the website isn't very informative, though. That's why I opted for including the "full type" there.