// #regions

[waderyan]

From @mbeckenbach on September 16, 2016 12:48

• VSCode Version: 1.5.2
• OS Version: Win10

Would be great to have //#region support in typescript

Copied from original issue: microsoft/vscode#12146

[waderyan]

@mbeckenbach can you provide more information of what you are looking for? I am not familiar with //#region support.

Also, is this VS Code specific or is this a feature request for TypeScript? This may be better in TypeScript.

[waderyan]

From @mbeckenbach on September 19, 2016 8:38

The full visual studio uses comments to mark code blocks as collapsable in all languages. Depending on the language, the syntax is slightly different as the comment syntax is different.

Hard to explain, but web essentials has a nice screenshot of regions in the javascript area: http://vswebessentials.com/features/javascript

Regions should exist for all languages. The comment syntax is different but the result schould be the same.

[waderyan]

From @divieirasilva on September 19, 2016 17:50

I think, @mbeckenbach are talking about the #region, current present on c# syntax of Visual Studio. Currently, on C#, #region name_region is used to tell where code will start folding and #endregion tells where code will stop folding.
I'm really missing this feature on VS Code as well, all my code have regions for better code reading and on VSCode I can't fold my regions.

e.g.

#region region_sample

void MyDummyMethod()
{
int a = 1 + 1;
}

void MyDummyMethod2()
{
int b = 1 + 1;
}

#endregion

In the sample above, the entire region block should fold and "region_sample" should be the label on folding.

[waderyan]

From @mbeckenbach on September 20, 2016 5:56

yes, that's what i'm talking about. i'm really missing that feature in other languages like for example ts

[waderyan]

@RyanCavanaugh I'm guessing you have thought about adding something like this before.

[mhegazy]

// #region support is really a webessentials feature. personally i find it fairly foreign to the JS language and tooling. implementing it is not straight forward, since these are comments at the end of the day. keeping the issue open awaiting more user feedback to see if there is enough demand.