Releases: Ayc0/Manatea
Releases · Ayc0/Manatea
v0.5.1-beta.2
What's Changed
- Revert type
Record<string, unknown>
introduced inv0.5.1-beta.1
Full Changelog: v0.5.1-beta.1...v0.5.1-beta.2
v0.5.1-beta.1
What's Changed
- Update all dev deps
- "@testing-library/react-hooks": "^7.0.2"
- "@types/jest": "^27.0.2"
- "jest": "^27.2.5"
- "prettier": "^2.4.1"
- "ts-jest": "^27.0.7"
- "typescript": "^4.4.4"
- Update microbundle to v0.14.1 -> add a
PURE
annotation on the react import in react-manatea - Remove
object
fromTea
and instead useRecord<string, unknown>
(minor breaking change) - Update TS config + update code accordingly
- Update GH actions versions to v2
Full Changelog: v0.5.0...v0.5.1-beta.1
v0.5.0 – Febreze (the big cleanup)
manatea
- All names changed: BREAKING CHANGE
createCup
->orderCup
,Change
->Order
(only in TS),- (and other internal names, please check the readme for the lexicon,
- when ordering a new cup with
orderCup
, you can now pass a flavoring function, Cup
was updated to receive 2 generics instead of one:FlavoredTea
andUnflavoredTea
(minor breaking change)- Remove
namedStores
BREAKING CHANGE, - Don't call
Object.freeze()
on the teas anymore (as it can mutate the provided value) (minor breaking change) - add
context
to servers and orders to avoid infinite loops when a cup's listener is used to update another cup
const cup1 = orderCup(0);
const cup2 = orderCup(0);
cup1.on((newTea, context) => cup2(newTea, context));
cup2.on((newTea, context) => cup1(newTea, context));
// Here updating cup1 will update cup2, and vice versa.
// But thanks to the `context`, we don't create an infinite loop,
// and the updates are dropped when they re-reached an already updated cup
-
use
Object.is
instead of===
for comparing the previous and the new teas (handleNaN
OOTB + differentiate-0
from+0
) (minor breaking change), -
add
sideEffects: false
in package.json to enable tree shaking
react-manatea
- update peerDependency to
[email protected]
- fix type in
useInfuser
useInfuser
exposes thecontext
(used to avoid infinite loops)- add
sideEffects: false
in package.json to enable tree shaking
internal changes
- update to yarn 3
- remove
lerna
and instead use custom scripts
Full Changelog: v0.3.6...v0.5.0
v0.5.0-beta.9 – Flavors of flavors
manatea
The flavoring
function accepts a second parameter: previouslyFlavoredTea
(which isn't passed for the initialTea
)
v0.5.0-beta.8 – A whole new Flavor
manatea
Flavoring
can transform a value from anUnflavoredTea
one to the storedFlavoredTea
Cup
was updated to receive 2 generics instead of one:FlavoredTea
andUnflavoredTea
- removed wrongly added
unstable_plate
react-manatea
useInfuser
,Infuser
, andinfuse
were updated to also supportFlavoredTea
andUnflavoredTea
Internal names
tea
->flavoredTea
previousTea
->previouslyFlavoredTea
teaRefill
->unflavoredTea
v0.5.0-beta.10 – The equalizer
manatea
- use
Object.is
instead of===
for comparing the previous and the new teas (handleNaN
OOTB + differentiate-0
from+0
) (minor breaking change) - properly use
FlavoredTea
inHandler
instead ofUnflavoredTea
(only type change)
internal names
Renamed more tea
into flavoredTea
v0.5.0-beta.7 – no side effects spotted
manatea
- add
sideEffects: false
in package.json to enable tree shaking - added by mistake
unstable_plate
react-manatea
- add
sideEffects: false
in package.json to enable tree shaking
v0.5.0-beta.6 – approved by peers
react-manatea
- update peer dep to v0.5.0-beta.6 instead of v0.5.0-beta.0
internal
- update all devDeps
- switch to yarn 3
- will keep the peer deps up to date with manatea
v0.5.0-beta.4 – infuse the context
react-manatea
- useInfuser exposes the context
v0.5.0-beta.3 – the one with names
manatea
All names changed BREAKING CHANGE
Exposed to users
-
createCup
->orderCup
-
Change
->Order
(only in TS)
Internal names
- cup's
listener
->server
-
setter
->flavoring
-
initialTea
->firstTea
-
newTea
->teaRefill