I noticed that like an hour ago. I just changed the template quote to use double quote and escaped double quotes and it worked. I remember trying before and didn't work right but the escape is working now. Based on looking at the characters though you shouldnt need to escape them but if it works then that is what I will use because it must be the way that angular parses the string that is the issue so to make it happy I ll escape them.
Thanks man! oh on more question. HOW THE HECK do you make your plunkers "public"? I need to learn how to use plunker, its pretty nice On Thursday, March 13, 2014 11:53:40 AM UTC-4, Justin Walsh wrote: > > Ok, I'm being silly. > > Its just the quote escaping that's the issue: > > See the updated plunkr<http://plnkr.co/edit/Xp535ccHOcmeA6bfbmY6?p=preview>: > http://plnkr.co/edit/Xp535ccHOcmeA6bfbmY6?p=preview > > On Thursday, March 13, 2014 5:47:57 PM UTC+2, Justin Walsh wrote: >> >> Hey Billy >> >> To be honest, I'm not sure if this has worked in previous releases of >> angular (I'm pretty new to angular myself). >> >> One thing that did pop into my head is the fact that angular expressions >> are like JavaScript expressions, but not strictly JavaScript >> expressions<http://docs.angularjs.org/guide/expression>. >> >> .... but then if you look at the this updated >> plunkr<http://plnkr.co/edit/Xp535ccHOcmeA6bfbmY6?p=preview>, >> it is possible to concatenate strings in an angular expression. >> >> The assumption that I'm making is that the label of ngOptions is parsed >> in the same way that angular expressions are parsed. But I could be wrong. >> I would need to look into the source. >> >> Justin >> >> On Thursday, March 13, 2014 4:44:38 PM UTC+2, Billy Figueroa wrote: >>> >>> Hey Justin thanks for the reply! Do you know why this seems to work >>> sometimes and not others? I have seen examples where this works and some >>> where it doesn't. Does the version of angular matter? Was this behavior >>> changed? I will try to use the function tonight when I get home, but I d >>> like to know why there is an inconsistent behavior with this expression >>> >>> could this be a bug? >>> >>> On Thursday, March 13, 2014 8:11:47 AM UTC-4, Justin Walsh wrote: >>>> >>>> Hi Billy, >>>> >>>> Doesn't look like you can do string concatenation in the label >>>> expression. >>>> >>>> But you could use a function: >>>> >>>> http://plnkr.co/edit/Xp535ccHOcmeA6bfbmY6?p=preview >>>> >>>> Does that help? >>>> >>>> Not sure if this is the correct place to put the function - (in the >>>> linking function - maybe someone else can comment) - but it works. >>>> >>>> Justin >>>> >>> -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
