5 Commits

Author SHA1 Message Date
8a14b6b824 restructure tree visit algorithm
Some checks failed
NeoVim tests / code-quality (push) Failing after 1m20s
2025-10-11 09:03:49 -06:00
fdb2a49638 Working better now (but see notes)
Some checks failed
NeoVim tests / code-quality (push) Failing after 1m18s
Even so, some things can get screwy if the component tree sets
suspicious `key`s. Like:

```lua
{
  'String 1',                    -- auto-assigned key = idx(1)
  h(Component, { key = 1 }, {}), -- conflicting key(1)
  'String 2',                    -- auto-assigned key = idx(3)
  h(Component, { key = 2 }, {}), -- key = 2
}
```

In this example, there are two elements competing for key `1`, which
causes weird render issues.
2025-10-09 22:49:01 -06:00
8fa2784bf7 WIP: react-like renderer
Some checks failed
NeoVim tests / code-quality (push) Failing after 1m23s
2025-10-08 23:48:18 -06:00
72b6886838 range: extmarks/tsquery; renderer: text-change
All checks were successful
NeoVim tests / code-quality (push) Successful in 1m18s
2025-10-02 20:01:40 -06:00
c760c495b7 update lua API to 1-based indices; add renderer
All checks were successful
NeoVim tests / plenary-tests (push) Successful in 11s
2025-05-04 15:44:09 -06:00