Opposite of Use Inferred Member Name (IDE0037)

[vsfeedback]

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

---

Add the opposite to Use Inferred Member Name. VS allows to simplify the expression and suggests to use the inferred member name. I would like to be able to transform code to unsimplify it

x.Select(o => new {
o.A,
o.B,
});

becomes

x.Select(o => new {
A = o.A,
B = o.B,
});

This is useful for readability and if you want to create a new type

---

Original Comments

Visual Studio Feedback System on 10/28/2019, 01:28 AM:

Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. We'll provide an update once the issue has been triaged by the product team.

[sharwell]

We have existing refactorings for 'Use tuple element name' and 'Add argument name'. It would be a natural extension of these features to have a refactoring to explicitly specify the name of an anonymous type member.