fix: don't count javascript template strings as atoms

[paperclover]

if template strings are atoms, changing the indentation of a block of code containing one counts that as a change, which is bad. instead, recurse the expression as normal.

not very happy with adding a special case to atom_from_cursor but i'm not familiar enough to know the right strategy.

test case

let x = `hello ${y
  ? 1
  : 2
}`;

{
  let x = `hello ${y
    ? 1
    : 2
  }`;
}

[hmknhovgd-boop]

إذا كانت سلاسل القوالب عبارة عن ذرات، فإن تغيير مسافة بادئة لكتلة من التعليمات البرمجية تحتوي على واحدة منها يُعتبر تغييرًا، وهذا غير مقبول. بدلاً من ذلك، قم بتكرار التعبير كالمعتاد.

لستُ سعيدًا جدًا بإضافة حالة خاصة، atom_from_cursorلكنني لستُ على دراية كافية بمعرفة الاستراتيجية الصحيحة.

حالة اختبار

let x = `hello ${y
  ? 1
  : 2
}`;

{
  let x = `hello ${y
    ? 1
    : 2
  }`;
}

#954

[Wilfred]

This usually doesn't work, unfortunately, which is why strings with interpolated expressions are treated as atoms in most cases.

The problem is that the text before and after the interpolation needs to be present in the AST, or difftastic won't understand that the following string literals are different.

`foo${name}`;
`foo ${name} `;

[paperclover]

The problem is that the text before and after the interpolation needs to be present in the AST, or difftastic won't understand that the following string literals are different.

works in the diff

though it does make whitespace only changes a bit harder to parse

actually, this one is tough. the underlines no longer appear

i do wonder whats a reasonable solution to this. the indentation showing up as a changed node is very unsatisfying.

[paperclover]

closing as stale on my part, not really sure of a good solution.