Hi!
The extension breaks //region //endregion comment folding.
# instead of // works, however both versions work without the extension.

Is there a specific reason for this, or a setting I should use? Or should I be using #?

    darkdog Hi, and thanks for reporting the issue.

    Both // and # should work. Let me check

    it seems // was not handled, will be fixed in the upcoming update!

    thanks

    fixed in the upcoming update, thank you!

    JakubMisek Does it work as expected now? I'm still getting issues with // and it doesn't behave as properly as vscode default. I need to add a space or some text after both //region and //endregion.

      a year later

      Hi,

      I don't seem to get '// #region' folding to work with the extension installed. Neither in PHP nor in HTML or JS sections inside a PHP file.
      Is there a setting I'm missing?

        Uwe I think it's either

        #region

        or

        // region

          JakubMisek Thanks for the swift reply.
          Actually, it's neither, plus, if the extension is disabled, all of the variants are working, even in HTML or JS parts of a php file.

            Uwe we don't provide regions for HTML/JS yet, but only outlines for PHP code:

            Isn't there another extension that might resolve the regions by itself?

              JakubMisek I was wrong when I said it was neither. You just shouldn't have anything between the comment opener and the keyword.
              Sadly, it is that restrictive, and yes, there may be other extensions enabling region folding, but on the other hand, VS Code supports that on its own.

              Thanks for your support and good luck to you!

                Uwe I mean if you don't have installed another extension, that may break it :-)

                  Write a Reply...