You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
can-stache at present allways applys livebindings it parses the string representation into a dom object to apply the bindings.
It would be really great if can-stache could be used like handlebars and only do livebindings and dom parsing and all that only in a browser environment.
maybe split all browser binding parts into a extra optional module.
The text was updated successfully, but these errors were encountered:
the size and bloat tickets from canjs and can-element are maybe related.as the dom and other binding parts take much code space.
as a workaround i am experimenting with template literals forking all existing canjs examples and do the binding via some self crafted helpers.
it works really well i think maybe even can-stache can be deprecated as your able to run functions inside template literals and also do if then else and the nativ js stuff.
can-stache at present allways applys livebindings it parses the string representation into a dom object to apply the bindings.
It would be really great if can-stache could be used like handlebars and only do livebindings and dom parsing and all that only in a browser environment.
maybe split all browser binding parts into a extra optional module.
The text was updated successfully, but these errors were encountered: