Timeline for Ruby variable in JavaScript throws syntax error
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 10:33 | history | edited | URL Rewriter Bot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Sep 13, 2014 at 1:52 | comment | added | C3roe | Whether or not ruby parsed it as a string doesn’t matter here – JavaScript is the context that you are introducing the value into here, and therefor you have to treat it according to the syntax rules of that context. | |
| Sep 13, 2014 at 1:37 | comment | added | Donato | @CBroe you are right, but at the time, I was expecting that value to be already parsed as string before it was rendered in javascript. | |
| Sep 13, 2014 at 0:02 | vote | accept | Donato | ||
| Sep 12, 2014 at 23:23 | review | Close votes | |||
| Sep 18, 2014 at 19:09 | |||||
| Sep 12, 2014 at 23:22 | history | edited | the Tin Man | CC BY-SA 3.0 |
deleted 11 characters in body; edited title
|
| Sep 12, 2014 at 23:08 | comment | added | C3roe | "Why isn't ruby evaluating this as a string?" – the context of the error is not Ruby, it’s JavaScript. And how do we write text literals in JS again ...? | |
| Sep 12, 2014 at 23:07 | answer | added | Gergo Erdosi | timeline score: 1 | |
| Sep 12, 2014 at 23:06 | history | asked | Donato | CC BY-SA 3.0 |