Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

feat(createRegistry): add move() method#149

Open
johnleider wants to merge 2 commits intomasterfrom
feat/registry-move
Open

feat(createRegistry): add move() method#149
johnleider wants to merge 2 commits intomasterfrom
feat/registry-move

Conversation

@johnleider
Copy link
Member

Summary

  • Adds move(id, toIndex) to createRegistry for positional reordering of registered items
  • Rebuilds Map insertion order and triggers optimized reindex via minDirtyIndex
  • Updates composable docs, rules, and proxy-registry pass-through list

Context

Prerequisite for createDataTable column ordering enhancement — enables createRegistry-backed column reorder without fighting append-only semantics.

Test plan

  • pnpm typecheck passes (both packages/0 and packages/paper)
  • pnpm test:run passes (3005 tests)
  • pnpm repo:check passes (knip + sherif)
  • Manual: verify docs page renders move() in API table

Adds `move(id, toIndex)` to createRegistry, enabling positional
reordering of registered items. Rebuilds Map insertion order and
triggers reindex with optimized dirty range.
@pkg-pr-new
Copy link

pkg-pr-new bot commented Mar 6, 2026

Open in StackBlitz

commit: a16db02

Add `if (needsReindex) reindex()` at the top of move() to ensure
ticket indices are current before the early-return check. Without
this, a deferred reindex from a prior unregister() could cause
move() to incorrectly skip the operation.

Also fixes TSDoc @see URL and proxy registry documentation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant