tko
tko copied to clipboard
knockout
🥊 Technical Knockout – The Monorepo for Knockout.js (4.0+)
With JSX (#25) and [jss](https://github.com/cssinjs/jss) we should be able to fully compartmentalize the code for components. I'm hoping to get this in for Beta-1, since once we're done catching TKO...
Which new features, something like native JSX/TSX support or Decorators does TKO offer?
I like the idea of [slots](https://vuejs.org/v2/guide/components-slots.html) for components, from Vue. Thoughts? @knockout/core @knockout/extended
I have a foreach binding that builds an array using the page count so I can enumerate using the new array. tko throws an error on the new keyword. ```...
It will borrow heavily from Vuex as a foundation. This will go as far as State, Mutations, Actions. ```javascript let store = { state: { myStoredObs: ko.observable(false) }, mutations: {...
I was asked to raise this issue https://github.com/knockout/knockout/issues/2456 here as well Hello, I am not aware how hard this could be to implement but I want to know if it...
From #1 , just so I can clean up relevant issues there. --- IanYates commented on Jul 6 It really depends on whether we're talking about writing the library in...
Noting @vvs [comment](https://github.com/knockout/knockout/issues/1533#issuecomment-325707170): > While we are at it, maybe a proper lifecycle for the components should be defined, not only a single onReady/afterRender? > Take a look at Vue.js...
KO needs some internationalization Note: - http://formatjs.io/ - http://i18next.com/ - http://stackoverflow.com/questions/11436685/ - http://stackoverflow.com/questions/16882171
The AttrProvider conflicts with the jsx provider i.e. ko-* in JSX will be made an attribute and interpreted by the attr provider as ko-*. This is the stop-gap workaround for...