Change log of the object-observer
by versions.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Issue no. 142 - added TypeScript type to exports declaration
- updated some minor dependencies
- updated the JustTest harness, the whole test suite is now running on NodeJS, Chromium, WebKit platforms
- updated the JustTest harness, the whole test suite is now running on NodeJS, Chromium, WebKit platforms
- introduced true JS privates instead of Symbol based ones
- moved deployment to the scoped NPM package
@gullerya/object-observer
- Issue no. 129 - graceful handling of the circular referenced inputs
- updated performance data on NodeJS
- upgraded dependencies
- upgraded dependencies
- reduced dependencies (via reworking build flow)
- improved CI
- Issue no. 121 - added commonjs module build
- upgraded dependencies
- upgraded dependencies
- Issue no. 86 - moved to the new JustTest testing framework
- upgraded dependencies
- Issue no. 113 - removed
observable
'sobserve
andunobserve
in favor of the static counterparts fromObservable
namespace.
- Issue no. 111 - Added
observe
andunobserve
methods as statics on theObservable
. Those methods will be removed from the next major release (5) from the observable instance and only be available fromObservable
namespace.
- upgraded dependencies
- Issue no. 106 - Fixed TS definition of ChangeType (enum to type)
- Issue no. 107 - Fixed TS definition of ObjectObserver.observe (options are optional)
- Issue no. 104 - Fixed TS definitions
- Issue no. 102 - Added TS definitions for convenience
- Issue no. 99 - simplified CD flow
- Issue no. 97 - removing the care for native objects, any but
Date
, due to seemingly non-relevancy (until proven otherwise); this effectively un-does issue #2
- Issue no. 53 - fixing failures on NodeJS due to
Blob
unavailability on global scope
- Issue no. 93 -
pathsOf
misbehave fixed
- dependencies updated
- performance tuned up
- dependencies updated
- dependencies updated
- Issue no. 82 -
object-observer
made cross-instance operable
- Issue no. 79 - added CodePen example for ObjectObserver API flavor
- Issue no. 81 - added integrity checksums to the CDN flow and documentation
- Issue no. 77 - manual CI trigger for release
- documentation improved and updated
- dependencies updated
- Issue no. 73 - added DOM-like API of
ObjectObserver
- documentation improved and updated
- dependencies updated
- Issue no. 71 - added CDN deployment
change
structure unified for all types of events- slightly improved performance
- Issue no. 70 - CI release automation flow improved
- performance tests adjusted
- performance tests
- Issue no. 65 - fixed a broken keys order of the cloned observable
- dependencies updated
- security process to be used - TideLift
- added automated release CI flow
- Issue no. 61 - removed the CommonJS-fashioned NodeJS distribution
- Issue no. 45 - implemented async flavor of changes delivery on per Observable configuration basis; default behavior remained the same - synchronous
- Issue no. 51 - batch delivery of
Object.assign
changes is enabled via the async opt-in, see issue #45 above
- Issue no. 58 - JSFiddle link to point to the latest
- Issue no. 55 - enhanced documentation of observation options
- Issue no. 56 - fixed handling of
pathsOf
option in case ofArray
massive mutations (reverse
,shuffle
events)
- enhanced tests and fixed mis-implemented negative ones
- Issue no. 46 - added support to the
TypedArray
objects - Issue no. 44 - added support to the
copyWithin
method (Array
,TypedArray
)
- slight performance improvements
- Issue no. 31 - added option to observe
pathsOf
, direct properties of a specific path only
- officially publishing and documenting Issue no. 33 - any nested object of an
Observable
graph is observable in itself
- Issue no. 29 - added experimental functionality of nested objects being observables on their own (not yet documented)
- Issue no. 29 - added experimental functionality of nested objects being observables on their own (not yet documented)
- Issue no. 29 - added experimental functionality of nested objects being observables on their own (not yet documented)
- updated performance numbers: slightly affected by the new functionality, Edge became obsolete while Chromium-Edge entered the picture, measured NodeJS
- Issue no. 28 - fixing non-observable objects detection
- minor improvenent in the CI part of the library due to newer/better version of the test runner