Repository navigation
|
Hi! our team migrated from ko to tko beta and got some issues in this progress. One was a "cannot bind to $parent" (don't remember to exact message right now). After some missleading error messages and debugging-time, we learned of the existence of the createChildContextWithAs option. That causes out problem, because the default is false and in the old behaviour it would be true. So why is the default false? Totally fine, when it's for Performance! But was it a design decision? |
Answered by
phillipc
Mar 7, 2025
Replies: 1 comment
|
The current default allows some tko features, see some tests like:
I would leave the default as it is, but a better readme is the way to go! |
0 replies
Answer selected by
phillipc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current default allows some tko features, see some tests like:
I would leave the default as it is, but a better readme is the way to go!