Releases: PimCoumans/DidUpdate
Releases · PimCoumans/DidUpdate
v0.11.0
Fixed issue with multiple update handlers on single compound ReadOnlyProxy
.
Full Changelog: 0.10.0...0.11.0
v0.10.0
- Fixed an issue with using a
WeakValueProxy
in a compoundReadOnlyProxy
. NowcurrentValue
is used properly. - Added
WeakReadOnlyProxy
to create weak proxies to read-only properties. These can also be created from aWeakValueProxy
. UseobservableValues.weak.yourProperty
to create one of these. The main use-case (and the best footgun so far) is when usingReadOnlyProxy.compound(...)
with local variables, as the compound read-only proxy stores the getter and introduces a retain cycle.
Full Changelog: 0.0.9...0.10.0
v0.0.9
- Updated
@StoredValue
to work more like@AppStorage
, only allowing specific values. Added a specific implementation that allows it to store aSet
value but stored as an array in theUserDefaults
store. - Small bugfixes to how
@StoredValue
is handled - Some
@ReadOnlyProxy
fixes, allowing to create these from@ExternallyUpdating
wrappers
Full Changelog: 0.0.8...0.0.9
v0.0.8
v0.0.7
Create a WeakValueProxy
automatically through type inference
Full Changelog: 0.0.6...0.0.7
v0.0.6
What's Changed
- @Storedvalue by @PimCoumans in #6
- WeakValueProxy by @PimCoumans in #7
Full Changelog: 0.0.5...0.0.6
v0.0.5
Improved way of accessing ObservableValues
through an extension on ObservableState
. Creating a local ValueProxy
can now be done through the observableValues
property on your ObservableState
model class
Full Changelog: 0.0.4...0.0.5
v0.0.4
- Support creation of value proxies from within your
ObservableState
object, no longer requiring you to go through its containing property wrapper - Added
ReadOnlyProxy
that acts as aValueProxy
for values that can not be updated or fromObservedValue
property wrappers that aren’t able to update the enclosing instance’s value directly
Full Changelog: 0.0.3...0.0.4