Releases: ryupold/vode
Releases · ryupold/vode
1.9.1
10 Jun 15:00
Compare
Sorry, something went wrong.
No results found
fix: resolve error boundary from old vode when new component fails to render
fix: first level dom evaluation
fix: standardize return values for tag() and children()
1.9.0
09 Jun 19:15
Compare
Sorry, something went wrong.
No results found
fix(catch): usage of 'catch' on the root vode with different Tag
NOTE: changing the root tag in vode during rendering is supported, but results in a new container node
to get a reference to the new container node: const newContainer = oldContainer._vode.vode.node
feat(state-context): add overload to context() for alternative substate targeting
1.8.12
25 May 14:23
Compare
Sorry, something went wrong.
No results found
fix: mergeClass with (1. object, 2. array)
1.8.11
25 May 11:23
Compare
Sorry, something went wrong.
No results found
feat: allow for async patches to be awaited by optionally returning a Promise
1.8.10
24 May 12:19
Compare
Sorry, something went wrong.
No results found
make patch function syncronous
it branches off to promises when necessary. this should result in a slight performance improvement
allow prop definitons to be falsy
makes writing conditional literals easier like: [DIV, condition && { class: 'xyz' }]
1.8.9
21 May 21:06
Compare
Sorry, something went wrong.
No results found
fix: ensure all queued state updates are reliably processed, even during ongoing renders
test: add test suite as esm build
1.8.8
19 May 16:18
Compare
Sorry, something went wrong.
No results found
fix: improve child rendering performance
fix: bug when a component function was reused in multiple memos
fix: setting an intermediate path to null via state context
fix: measure time with performance api
remove ability to memo prop objects as this could lead to undecidable situations during rendering
update documentation and add more tests showing advanced features
1.8.7
16 May 22:50
Compare
Sorry, something went wrong.
No results found
fix: rework onMount/onUnmount lifecycle
fix: nested memo calls with unmount handlers
1.8.6
16 May 13:47
Compare
Sorry, something went wrong.
No results found
fix: execute onUnmount reliably (symmetric to onMount)
fix: in certain situations onMount was called multiple times in initial render
1.8.5
14 May 19:46
Compare
Sorry, something went wrong.
No results found
fix: allow higher order component functions to use memo
You can’t perform that action at this time.