refactor: :fire: Removed initializeMemberFromCtor command

[KreativJos]

initializeMemberFromCtor is provided by the C# extension (omnisharp)

75

[KreativJos]

Don't know about versioning with this, but I do not think it really matters. I don't expect anyone to have an issue with this, because the feature is included in the default C# extension.

[bard83]

It won't matter exactly for the reason you mentioned. Probably redundancy should be considered as a bug. Omnisharp has an higher priority/consideration compared to the extension.

[bard83]

Don't know about versioning with this, but I do not think it really matters. I don't expect anyone to have an issue with this, because the feature is included in the default C# extension.

I've miss understood on the first round, I guess that your retro-compatibility concern is more related to the following situation: the user does not have the specific C# extension version - where the initialization feature for ctor exists - but it gets this change -> the user might loose the feature because none provides it. Possible approaches:

• don't care about it: the user will downgrade the version in case (risk is that the user might uninstall the extension because it gets disappointed with the decision and also could struggle with future updates).
• opt-in configuration flag: show the feature in case the configuration is flagged (currently omnisharp is the de facto standard c# extension for vs code and the choice to remove the feature relies on it, but what will happen in case it won't be anymore in the future?).
• show the feature smartly: check whether omnisharp provides it (check the omnisharp version? don't know...) or does not.

To me the second could be the correct decision, don't know if it's technically doable.