Notas de la versión 0.5 de Yoltra

#0.5.0 (2026-08-15)

#@yoltra/core

Funcionalidades

• Teaches the path types the difference between a value with an addressable interior and one without.\n\nA Map or Set keeps its contents outside its own enumerable keys, so walking one with keyof yielded the names of its methods: byId.get and byId.size were offered as subscribable paths, and a slice holding a plain number autocompleted toFixed. None of them could ever fire, because the diff reports such a value at its own path and never descends into it. The new RootValue type states that rule once, and Path and Dotted both defer to it.\n\nDotted now resolves to the empty path for a slice that IS one value, so { reducer, property: "" } type-checks where it can actually fire instead of falling through to the untyped overload. The conditional distributes, so a nullable object slice gets both "" and its keys, which is correct: it changes at its root when it becomes null, and at a leaf otherwise. PathValue<T, ""> now resolves to T, matching what both path readers have always returned for an empty path; it used to say never.\n\nNo path that resolved before stops resolving. Pinned by membership assertions in the type tests, which name each path individually so a single one appearing or vanishing is a build failure.

#@yoltra/react

Funcionalidades

• Picks up the corrected Dotted and PathValue from @yoltra/core, so useAtomicProp({ reducer, property: "" }) on a slice that holds a single value returns that value's type rather than unknown, it used to miss the typed overload and fall through to the property: string one.\n\nInference through an object slice is unchanged, and is now pinned: type-level tests assert the resolved type of every path form (nested leaf, array index, whole array, whole Map, and the accessor form) through createYoltra, the way an application actually gets its hooks.