Giters
gullerya
/
data-tier
2-way data binding framework for web (HTML/JS)
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
11
Watchers:
3
Issues:
64
Forks:
1
gullerya/data-tier Issues
[ci/cd] improve the ci/cd by removing custom code in favor of a standard npm version
Closed
2 years ago
ci: move to new just-test and enhance tests
Updated
3 years ago
add symmetric handling for class attribute as className property
Closed
3 years ago
Comments count
1
events: spec out and implement
Closed
3 years ago
attributes: spec out and implement
Closed
3 years ago
Comments count
1
documentation: take out and specify as separate API the tying declaration
Closed
3 years ago
chore(test): add test for the newly added 'data-' attributes support
Closed
3 years ago
Comments count
1
need a possibility to explicitly prevent data-tier from processing some subtree
Updated
3 years ago
optimize addView / delView logic in views service
Closed
3 years ago
chore(ci): replace 'release' trigger with manual dispatch
Closed
3 years ago
expose Observable that data-tier works/bundled with
Closed
3 years ago
Comments count
1
ci: add deployment to the CDN
Closed
3 years ago
explore possibility to create ties from primitives
Closed
3 years ago
Comments count
1
ensure it is possible to create/update with empty null or undefined model
Closed
3 years ago
docs - update documentation of the new change event syntax
Closed
3 years ago
better events (view to model) binding API
Closed
3 years ago
chore: automate release version management
Closed
3 years ago
Comments count
1
smarter DOM changes processing needed
Closed
4 years ago
Comments count
2
add some measurable benchmark / performance tests
Updated
4 years ago
add version of the 'data-tier' to the runtime
Closed
4 years ago
scope tying is not working when model created for a non-appended view
Closed
4 years ago
Comments count
1
ensure update not fails on scoped key update
Closed
4 years ago
Comments count
1
ties.update should return an observable not plain original
Closed
4 years ago
Comments count
1
add an API to replace the ties model completely
Closed
4 years ago
Comments count
1
add global tracking and warning on duplicate ties definitions
Updated
4 years ago
document latest changes
Closed
4 years ago
Comments count
1
add convenient 'ties.obtain' API
Closed
4 years ago
Comments count
1
add special handling of the classList tying
Closed
4 years ago
Comments count
1
improve changing tie attribute on the views
Closed
4 years ago
Comments count
1
add functional interface tying
Closed
4 years ago
Comments count
2
full path update is somewhat cumbersome - tech improvements
Closed
4 years ago
Comments count
1
tying model as a root do not work - due to refactor?
Closed
4 years ago
Comments count
1
add global level stat collector to clarify multiple instances usage
Closed
4 years ago
Comments count
1
tie's model better to be nonassignable and have special APIs to (re)set it as a whole
Closed
4 years ago
Comments count
1
show an error when same element's property multi-tied
Closed
5 years ago
Comments count
1
misbehave observed when non existing path specified
Closed
5 years ago
Comments count
1
when processing added nodes - skip style elements
Closed
5 years ago
Comments count
1
no updates performed when tied to the nested path but tie root is replaced
Closed
5 years ago
Comments count
1
custom default tie property and custom change event
Closed
5 years ago
Comments count
1
shadow DOM hosts that defined AFTER the tying are not handled correctly
Closed
5 years ago
Comments count
1
root document `MutationObserve`ed twice
Closed
5 years ago
Comments count
1
when shadow dom scanned for tied elements it fails
Closed
5 years ago
Comments count
1
shadow DOMs are not "mutation observed" by data-tier
Closed
5 years ago
Comments count
1
Shadow DOM - rethought design
Closed
5 years ago
Comments count
1
when tie is not defined data-tier should NOT do a thing
Closed
5 years ago
Comments count
1
verify and gracefully handle already removed tie in discard flow
Closed
5 years ago
Comments count
1
provide well-defined API to allow subscription for change event on custom element
Closed
5 years ago
Comments count
1
provide default target property for a short tying syntax
Closed
5 years ago
Comments count
1
primitive bindings may assume default target property
Closed
5 years ago
Comments count
1
property 'href' should be handled specially
Closed
5 years ago
Comments count
1
Previous
Next