Nesting snippets breaks ChoiceNodes

[anthony-S93]

The desmonstration below uses the following snippets:

s(
        {
            trig = "eq"
        },
        {
            c(1, {
                sn(nil, {
                    t({"\\begin{equation}", "\t"}),
                    r(1, "body"),
                    t({"", "\\end{equation}"})
                }),
                sn(nil, {
                    t({"\\begin{equation*}", "\t"}),
                    r(1, "body"),
                    t({"", "\\end{equation*}"})
                })
            })
        },
        {
            stored = {
                ["body"] = i(1, "body")
            }
        }
    ),

    s(
        {
            trig = "test"
        },
        {
            t("test node")
        }
    ),

When tested, the snippets exhibited the following behavior:

2025-04-30-20-28-39.mp4

After another snippet is passed into an insertNode that is residing within a choiceNode, switching choices using luasnip-next-choice will work only one time before failing.

Is this by design? Are the entries in a choiceNode not meant to contain other Luasnip snippets?

-- Luasnip configs

local luasnip = require("luasnip")

    -- Set default snippet location
    require("luasnip.loaders.from_lua").lazy_load({
        paths = "~/.config/nvim/snippets"
    })

    -- Configurations
    luasnip.config.set_config({
        keep_roots = true,
        link_roots = true,
        link_children = true,
        exit_roots = false,
        enable_autosnippets = true,
        delete_check_events = "TextChanged,InsertEnter",
        updateevents = "TextChanged,TextChangedI",
        region_check_events = "CursorMoved"
    })

[L3MON4D3]

Hi! :)

That is indeed a bug (and one that is relatively simple to hit, I'm surprised!), the snippet should be turned into just text, but this should not cause an error. I'll push a fix :)

If you want to test some new features, in #1137, the snippet isn't even turned into text, but can stay active :)