Changelog of data-tier as per release.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- refactored publishing to the scoped one
- updated tests to the new framework
- update CI to the best practices
- documentation updated
- dependencies updated
- CI adjusted to better practice, BUT tests were disabled to to very outdate test framework and move to the scoped v4
- dependencies updated
- CI adjusted to better practice
- dependencies updated
- dependencies updated
- Issue #75 - implemented tying declaration API - events
- documentation updated
- dependencies updated
- Issue #79 - implemented tying declaration API - attributes
- removed special treatment for the
data-attributes (in favor of well defined attributes support API) - documentation updated
- dependencies maintanance
- Issue #74 - added tying declaration API - specification
- Added special treatment for the
data-attributes (thanks Piotr Pazola) - sets the value on the attribute rather than property - dependencies maintanance
- removed
addRootDocument/removeRootDocumentin favor ofaddDocument/removeDocumentAPIs (deprecated since 2.11.0) - Issue #56 - internal implementation improvements
- documentation updated
- dependencies maintanance
- Issue #70 - added manually triggered release
- documentation updated
- dependencies maintainance
- documentation updated
- dependencies maintainance
- Issue #68 - exposing
Observableimplementation that is bundled with thisdata-tierversion cache-controladded to the CDN deployment
- Issue #58 - allowed to create/update ties with primitive model (
boolean,number,string); won't throw now and will corretly do a ties updates - Issue #59 - capable of create/update ties with
null; won't throw now and will correctly do a ties updates nullishmodel values (undefined,null) transformation into an empty string is now limited to only:textContenttarget property for any elementvaluetarget property for only these:INPUT,SELECT,TEXTAREA
- Issue #60:
- removed
defaultTieTargetproperty support (less intrusive approach aggenda) - removed
changeEventproperty support (less intrusive approach aggenda) - added new syntax to specify the event to listen to per tied property
- added support for multiple events as per multiple properties tied
- removed
- updated dependencies
- Issue #61 - release version automation
- updated dependencies
- Issue #53 - version to the runtime
- Issue #41 - thoroughtly revised DOM processing mechanics
- updated dependencies
addRootDocumentAPI, (useaddDocumentinstead)removeRootDocumentAPI, (useremoveDocumentinstead)
- security process to be used - TideLift
- updated dependencies
- added release automation
- removed Travis CI (in favor of GitHub actions)
- Issue #50 - fixed a scoped views lifecycle, case when view added before the model
- upgraded dependencies
- Issue #49 - fixed a new API:
DataTier.ties.update(key, newModel);which misbehaved when non-existing scoped (element) key provided - upgraded dependencies
- implemented Issue #48 - fixed a new API:
DataTier.ties.update(key, newModel); - upgraded dependencies
- Issue #42 - added a possibility to update tie's model as a whole via new API:
DataTier.ties.update(key, newModel); - upgraded dependencies
- upgraded
object-observerdependency, bearing an important, yet meanwhile experimental, functionality for a repeater like consumers
- adding experimental scoped tying capabilities - not yet publically available
- Issue #40 - documented all of the latest changes, verified functional tying documentation
- add full tutorial example and improved tutorials description (should add more use-cases in the future)
- Issue #39 - added support for a
classListin a special manner
- changed behavior of the nested properties change when parent is watched - now parent is also notified
- Issue #37 - fixed mishandlings of the
data-tieproperty changes - attempting to push performance further (switched model change observer definition from
bindto lambda syntax)
- Issue #36 - method/function based tying
- enhanced tests coverage
- performance tunings
- documentation improved and enhanced
- added full test coverage for a tie params
- Issue #34 - tying the model at the root level
- minor documentation improvements
- documentation improvements and enhancements
- issue #29 - removing non-convenience and ambiguity in API usage
This point (
2.0.0) is an API breaking point! Please refer to the API documentation.
-
1.14.0
- upgrading
object-observerdependency, which has a fix for a proper handling of an Error objects
- upgrading
-
1.13.1
-
1.12.1
- moved to newer version of
just-test, providing real tests in CI and coverage now
- moved to newer version of
-
1.12.0
- upgraded dependencies (specifically
object-observerincluding some important fixes)
- upgraded dependencies (specifically
-
1.11.0
- performance tuning and preventing potential double processing of child nodes
-
1.10.0
- upgraded dependencies (specifically
object-observerincluding some important fixes)
- upgraded dependencies (specifically
-
1.9.0
- upgraded dependencies (specifically
object-observerincluding some important fixes)
- upgraded dependencies (specifically
-
1.7.1
-
1.7.0
- fixed issue #25 - yet another issue with the nested tied elements within shadow DOMs
-
1.6.2
- fixed issue #24 - adding
MutationObserverto any shadow DOM (or even any document root) added to thedata-tier
- fixed issue #24 - adding
-
1.6.1
- implemented issue #23 - auto-tying/untying the open shadow DOM during the addition/removal of the host elements to the living DOM; providing APIs to explicitly add/remove shadow DOM for a closed shadow DOM case and for the elements that the shadow DOM is attached to them 'post-factum' (when they are already in the living DOM)
-
1.5.0
- added default target property
srcfor the following elements:iframe,img,source
- added default target property
-
1.4.2
- performance improvements (mainly in the area of collecting new view from DOM)
- improved print outs to clarify the library boot process/times
- add initial experimental implementation of support for a micro frontend design patterning issue #3
-
1.4.1
- implemented issue #21 - missing
Tiewon't do anything with tied elements - allowing to work with multiple unrelated instances ofDataTierin the same application (microfrontends - we are coming!!!)
- implemented issue #21 - missing
-
1.3.0
-
1.2.0
- fixed an issue where single element mapped to few different ties was not updated correctly
- upgraded dependencies
-
1.1.2
- upgraded
object-observerdependency to2.0.2, having some essential fix for issue #20
- upgraded
-
1.1.0
- upgraded
object-observerdependency to2.0.0, which affects the support matrix - fixed an issue with not-yet upgraded customized elements (not ideal, but works, waiting for spec to have it ideal)
- upgraded
-
1.0.3
- Fixed issue no. 15
- Improved error handling during elements collection in order to not break the flow due to a single failure
-
1.0.2
- Fixed issue no. 14
-
1.0.0
- First release to hold an ES6 module flavor distribution only (pay attention to the library loading)
- Fixed view -> model flow for
inputof typecheckbox - Fixed an error in the log where non-tied elements were removed from DOM
-
0.6.25
- Fixed issue no. 13
-
0.6.22
- initial provisioning of ES6 module
- new API defined and implemented in ES6 module distribution
-
0.6.19
- Fixed incorrect behavior when
tie-propertyconfigured on the element after it was added to the DOM
- Fixed incorrect behavior when
-
0.6.18
- Fixed issue no. 12
-
0.6.17
- Added
tie-propertyOOTB controller - having parameter syntaxpath.to.data => propNameit is made possible to tie to arbitrary element property (yes, this is havingCustomElementsin mind)
- Added
-
0.6.16
- Fixed potential issue with empty (
null) object traversal in deep tying
- Fixed potential issue with empty (
-
0.6.15
- Fixed issue no. 11
-
0.6.14
- Fixed defect in
tie-listcontroller when text nodes present in thetemplateelement - Added
tie-datetime-textOOTB controller
- Fixed defect in
-
0.6.13
- Added
tie-inputOOTB controller in other to track an immediate changes in input elements supportinginputevent (types:text,passwordofinputelement,textareaelement).
- Added
-
0.6.12
- Fixed issue no. 10
- Further performance improvements
-
0.6.11
- Fixed issue no. 8
- Fixed issue no. 9
- Minor performance improvements
-
0.6.10
- Added a possibility to create/update Tie's data with a plain JS object, in this case
data-tierwill attempt to auto-create and useObservablefrom it, using an embeddedObservableimplementation - Fixed issue no. 7
- Added a possibility to create/update Tie's data with a plain JS object, in this case
-
0.6.9
- Conceptually
Rulehas been replaced byController. There are still no API changes with regard to that, nor any API are yet published, but there will be some refactoring in this area in future releases - Fixed issue no. 6, some performance improvements made for a large scale DOM manipulations
- Conceptually
-
0.6.8
- Fixes: issue no. 2 (smooth handling of an empty values given to the controllers definition), issue no. 4 (non working repeaters on subgraph list), issue no. 5 (improvements of
data-tie-classes)
- Fixes: issue no. 2 (smooth handling of an empty values given to the controllers definition), issue no. 4 (non working repeaters on subgraph list), issue no. 5 (improvements of
-
0.6.7
- Added a possibility to create a tie without providing any initial data, for early setup with lazy data provisioning
-
0.6.5
- Fixed a case that element having no dataset breaks the views collection flow (this is not a valid case, but see this issue in Edge, so got to be defensive here)
- Added
tieSrcrule and removed obsoletetieImagerule (did the same astieSrc, just in a less general flavor) - Added
tieHRefrule - Added
tieClassesrule
-
0.6.0
- Moved to
object-observer.jslibrary as an observation engine, were impacted both the API and the implementation.
- Moved to
- 0.5.41
- First version, based on native
Object.observetechnology.
- First version, based on native