These are chat archives for canjs/canjs

27th
Oct 2015
Josh Dean
@imjoshdean
Oct 27 2015 16:09
So I attempted to update CanJS from 2.2.9 to 2.3 this morning and ended up getting a weird "[my app's path]/@loader/@loader.js file not found" error
Am I missing something with this? cc @daffl @justinbmeyer
Perhaps something I need to set up in my steal config?
Ryan Wheale
@DesignByOnyx
Oct 27 2015 16:30
upgrade steal to 0.12
@imjoshdean ^
Matthew Phillips
@matthewp
Oct 27 2015 16:31
That's one option, or you can add a map in your config
Ryan Wheale
@DesignByOnyx
Oct 27 2015 16:31
blob
Matthew Phillips
@matthewp
Oct 27 2015 16:31
System.config({ map: "@loader/@loader": "@loader" })
Josh Dean
@imjoshdean
Oct 27 2015 16:32
@matthewp's answer is the more acceptable
I'll give that a shot
Matthew Phillips
@matthewp
Oct 27 2015 16:32
err, missed a {} in there, but you get the point
Josh Dean
@imjoshdean
Oct 27 2015 16:36
That got me to the next checkpoint, thanks @matthewp
Ryan Wheale
@DesignByOnyx
Oct 27 2015 16:37
@matthewp - I haven't tested it yet, but isn't this issue present with all of the @-prefixed modules? I was able to fix it in the steal source on my end by not normalizing modules names which began with @.
Matthew Phillips
@matthewp
Oct 27 2015 16:40
no, the issue is just with steal syntax, which the stache plugin is using
0.11+ just includes the same map I showed above
Josh Dean
@imjoshdean
Oct 27 2015 16:57
@matthewp did CanJS 2.3 suddenly get TREMENDOUSLY more picky about what it considers acceptable HTML?
Matthew Phillips
@matthewp
Oct 27 2015 16:57
not to my knowledge
Josh Dean
@imjoshdean
Oct 27 2015 16:58
I'm suddenly running into issues where things that were acceptable (for one reason or another) in 2.2.9 are no longer acceptable in 2.3
Matthew Phillips
@matthewp
Oct 27 2015 16:58
there was always a problem with putting block elements inside of inline elements I believe
Josh Dean
@imjoshdean
Oct 27 2015 16:58
e.g.
Matthew Phillips
@matthewp
Oct 27 2015 16:58
like what?
Josh Dean
@imjoshdean
Oct 27 2015 16:58
<option value={{.}}>{{.}}</option> is no longer acceptable
have to convert that to <option value="{{.}}">{{.}}</option>
Matthew Phillips
@matthewp
Oct 27 2015 16:58
hm
Josh Dean
@imjoshdean
Oct 27 2015 16:58
<div {{#isSomeCondition}} property {{/isSomeCondition}} /> no longer acceptable
but <div {{#isSomeCondition}}property{{/isSomeCondition}} /> is
Matthew Phillips
@matthewp
Oct 27 2015 16:59
I would submit a bug, I doubt these are on purpose
Josh Dean
@imjoshdean
Oct 27 2015 17:04
...except I can't reproduce in a JSBin, naturally
Justin Meyer
@justinbmeyer
Oct 27 2015 17:23
@imjoshdean @matthewp <div {{#isSomeCondition}} property {{/isSomeCondition}} />is going to be difficult to fix
at least without adding some stache logic to can.view.parse
I'm sorta surprised it was working before
so might be possible to make work
but the issue is that can.view.parse doesn't know if {{}} is a {{insert}} or a {{#sectionStart}}
it just sees {{}}
Justin Meyer
@justinbmeyer
Oct 27 2015 17:35
but yes, @imjoshdean please create an issue