Commit 62c808db authored by James Laver's avatar James Laver

v0.4.2 - see changelog

parent 1d77097e
...@@ -72,6 +72,7 @@ Not in any particular order ...@@ -72,6 +72,7 @@ Not in any particular order
* Test consumer (we only test useContext right now) * Test consumer (we only test useContext right now)
4. Misc hooks 4. Misc hooks
* Test useEffect/useLayoutEffect are fired at the correct stage * Test useEffect/useLayoutEffect are fired at the correct stage
* Test useEffectOnce/useLayoutEffectOnce are fired once
* Test useMemo/useCallback * Test useMemo/useCallback
* Test useImperativeHandle * Test useImperativeHandle
* Test useDebugValue * Test useDebugValue
...@@ -88,6 +89,17 @@ Not in any particular order ...@@ -88,6 +89,17 @@ Not in any particular order
<!-- * `R.React.provide` - provider a value through a `Provider` --> <!-- * `R.React.provide` - provider a value through a `Provider` -->
<!-- * `R.React.consume` - consume a value through a `Consumer` --> <!-- * `R.React.consume` - consume a value through a `Consumer` -->
### 0.4.2
New:
* `useEffectOnce` (+ layout and prime variants) - effects which run
once at component mount and cleanup once at component dismount.
* `unsafeUseEffect`, `unsafeUseLayoutEffect`, `unsafeUseMemo`,
`unsafeUseCallback`, `unsafeUseImperativeHandle` - unsafe hook
variants where you pass an array-like object of memo values without
any help from the type system to assert such likeness to an array.
### 0.4.1 ### 0.4.1
New: New:
......
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment