The other is "scope.root.loginSession.user.email".
yes thats a bug if node env is not set
if it is set this don't shows
create a user and a tournament
you will see that it warns on any value
all the form data everything
but it will all work and render
so the value is there but it warns its not in scope
it even complains about scope.root.values
that they are not there but it renders the {{scope*}}
I see a few different scenarios here
where it looks and all that
so i can't do a lot about that i would need to understand stache parser probally
but i am sure its only a little thing but it needs to get found
as that worked befor relativ good
in 3.0
some one has a idea how to fix this:
can-observation.js:255 Uncaught TypeError: Cannot read property 'valueDependencies' of undefined
at Function.Observation.updateChildrenAndSelf (can-observation.js:255)
at eval (can-observation.js:257)
at Set.forEach (<anonymous>)
at Function.Observation.updateChildrenAndSelf (can-observation.js:256)
at Observation.get (can-observation.js:156)
at Object.getValue (get-set.js:147)
at Text.branchRenderer (mustache_core.js:329)
at Text.HTMLSection.targetCallback (html_section.js:151)
at hydrateCallbacks (can-view-target.js:254)
at Object.hydrate (can-view-target.js:276)
i have a property editingCard that a set via a event = card
then the stache template has a if clause for if editingCard
it works well i am also using that exact same code and stuff in other components
when i now call removeEdit()
which does this.editingCard = null
this error happens
:D
you would need to apply@bitovi i think justin is the CEO
you can apply also for me
Simply put in your message frank also wants work :sparkles:
as the current channel topic here is broken because of usage of canjs 4 as it uses latest
hey, I am using can-fixture and I was wondering how to avoid getting stringified responses. for example:
let statuses = {
success: 1,
statuses: "anything really, just testing!"
}
fixture({method: "get", url: "/json/internet/blah/blah/blah"}, function() {
return statuses
});returns statuses as a string
Can someone explain visible difference between can observables and stream functionality ? LIke Kefir streams / toStream etc. What is possible with streams that isn't possible with observables ?
For example here: https://canjs.com/doc/guides/technical.html in section where redux-like approach described. There is point:Having a single, ApplicationViewModel that contains all state, derived using can-define-stream from events dispatched on the ApplicationViewModel.
I cant understand why we need can-define-stream here ? Any observable will have change event as well.
like in 4.0 there is
value stream added. But you could have same functionality in set before, isn't it ?
well...if your value was list pushing new items there didn't call
set and with value it may be different, but still