Hacker News Reader

Comment by stevebmark | Hacker News Reader

    data-actions-on-response="
      mapToTemplate('${someResponse.body}', '#box');
      showElms('#box');
      logToConsole('statusCode:', '${someResponse.statusCode}');
    "

oh my god

View on HN

Looks familiar,

  someAttributeNvmWeCallThemProps={(someResponse) => {
    mapToTemplate('${someResponse.body}', '#box');
    showElms('#box');
    logToConsole('statusCode:', '${someResponse.statusCode}');
  }}

Sure it is similar to JS/React, but you're missing out on lint tools, TS, flow, reasonml, or other tools that help you catch errors.

I don't know why React people always say that unless you're using JSX you miss out on lint tools. VueJS templates use "" instead of {} but you still get all the lint tools you'd expect.

no, this looks like a nightmare leaky abstraction imperative API with non statically analyzable code like '#box'

#box is just a selector, it means element with id box, and you can see errors like "element is not found" anyway

I'm assuming it evals it, or runs it through some parser and does parameter replacement before executing.

it evals, but only some part of it, so it prevents XSS attacks

Reply on news.ycombinator.com