Intellisense bug: when contents of string interpolation contains newline, the final double quote is incorrectly moved

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

Example:

_logger?. LogError($"{guid} failure: {await httpResponseMessage
. Content
. ReadAsStringAsync()
. ConfigureAwait(false)}");

... becomes...

_logger?. LogError($"{guid} failure: {await httpResponseMessage
. Content
. ReadAsStringAsync()
. ConfigureAwait(false)}
");

... on save. This doesn't compile.

---

Original Comments

Visual Studio Feedback System on 11/10/2019, 10:15 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

---

Original Solutions

(no solutions)

[davidnmbond]

It's also worth noting that string interpolation does not currently support newline characters, though I can see no logical reason why not.

[CyrusNajmabadi]

@davidnmbond What do you mean by that? You can both embed newline characters with an escape like so:

                    var v = $"foo\nbar";

Or you can directly embed a newline like so:

                    var v = $@"foo
bar";

This matches how normal strings work.

[davidnmbond]

I mean:

    var text =$"They list of people includes: {(string.Join(", ", people.Where(p=>p.IsHappy)
        .OrderBy(p=>p.Surname)
        .ThenBy(p=>p.Forename)
        .Select(p => $"{p.Forename} {p.Surname}"))}.  They are all happy.";

There are no newline characters in the output string, but adding length Linq mid-interpolated string is a pain because you have to keep it all one one line. There is no real need for this constraint.

[CyrusNajmabadi]

There is no real need for this constraint.

Yes there is. You have a normal interpolated string. So the lexer isn't going to consume newlines in the middle since that's not allowed there. If you want this, you can write it as:

                var text = $@"They list of people includes: {
                    (string.Join(", ", people.Where(p => p.Length > 21)
                    .OrderBy(p => p.Surname)
                    .ThenBy(p => p.Forename)
                    .Select(p => $"{p.Forename} {p.Surname}")))}.  They are all happy.";

@ strings can span multiple lines in C#, non-@ strings cannot. That's regardless of whether they're interpolations or not.

[CyrusNajmabadi]

This part doesn't make sense:

... on save. This doesn't compile.

We don't manipulate code on save. So this must be some other tool. Need more info on a repro that causes this.

[ghost]

Closing this issue as we've seen no reply to the request for more information. If you are able to get the requested information, please add it to the issue and we will retriage it.