Vscode-jupyter: Make cells collapsible in python files

[oerpli]

Environment data

• VS Code version: 1.33
• Extension version (available under the Extensions sidebar): Current
• OS and version: Win10 1703
• Python version (& distribution if applicable, e.g. Anaconda): Anaconda 3.7
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): Conda
• Relevant/affected Python packages and their versions: n/a
  

  Expected behaviour

In a document with multiple cells, collapsing some of them improves usability.

Actual behaviour

It is not possible to collapse cells.

Some Details

I think defining #%% as (collapsible region start) shouldn't be very hard (I can try to submit a PR in 1-2 weekends if you agree with the idea).

Some implementation details should be evaluated though:

• Behavior of Shift+Enter in the cell above
• What to display if a region is collapsed (#%% Comment ... would be the default I think)
• Behavior of collapsed regions affected by Run below|above
• Visibility of Run Cell | Run Above | Run Below

[rchiodo]

I believe the only way to do this would be with the outline support VS Code has already:
https://code.visualstudio.com/api/references/vscode-api#FoldingRangeProvider

As far as I can tell, the start line remains visible, so you'd probably end up with something like:

%%

%%

%%

With no clear indication what cell was what. Maybe combined with a decorator provider, it could also stick in the first line of code after the cell header.

[Diogo-Rossi]

I am also waiting for this feature. It may be simple as described by @DonJayamanne in microsoft/vscode-python#10503

As far as I can tell, the start line remains visible, so you'd probably end up with something like:

%%

%%

%%

With no clear indication what cell was what. Maybe combined with a decorator provider, it could also stick in the first line of code after the cell header

The feature may be very similar to the #region/#endregion folding, already supported (#33).
Like in #region folding, it could accept comments after key word that defines the cell.

[richarddwang]

Is there anything new ? This should be set to important because I believe most of data science and ml guys write long jupyter notebook. And we are used to collapse those cells in Colab.

[rchiodo]

Sorry but this isn't on our radar at the moment. It's waiting for more people to up vote it.

[BBirdselllab]

I upvoted. Both the other notebook platforms I use, Google Colabs & Mathematica, have this feature natively. The reasoning is sound: A lot of times in data sci applications certain cells are no longer required to be updated frequently and it reduces clutter. Not being able to collapse cells in VS Code's implementation of Jupyter notebooks has been being bugging me for months, and I was just thinking this weekend about porting some project files over to Colabs because it's a cleaner coding experience. It can't really be considered an edge feature request anymore. It's a minimal viable product requirement now in my opinion.

[Yannl]

I upvoted. It is the reason preventing me to use VSCode as a notebook editor.

The Microsoft team working on https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-github-issue-notebooks already implemented collaspsible section as well as drag and drop of cells in notebooks. (cf screenshot or VSCode insider required to test for now) Could you reuse their work?

[rchiodo]

The Microsoft team working on https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-github-issue-notebooks already implemented collaspsible section as well as drag and drop of cells in notebooks. (cf screenshot or VSCode insider required to test for now) Could you reuse their work?

Yes this is the plan. We'll be using that same API to rewrite how we support jupyter notebooks.

[mmcguffi]

Is there any update on this? I agree with previous comments that this is a huge headache when using VScode for Jupyter notebooks

[DonJayamanne]

For those interested, our long term plan is to use the VS Code Notebook API for Jupyter Notebooks.
More information can be found here:
https://github.com/microsoft/vscode-python/issues/10496
https://github.com/microsoft/vscode-python/issues/12189

[rchiodo]

It should be noted that this issue microsoft/vscode-python#5227 is actually about adding another collapse region into a python file with cells. Cells are usually delineated with # %%.

This issue is not actively being pursued by our team but we welcome PRs if somebody else finds the time to get to this.

[PrateekArya]

@rchiodo Not sure if u are joking or serious but I think the original request was about collapsing the cells only. 😊

Also, isn't this same as microsoft/vscode-python#10503 and microsoft/vscode-jupyter#957??

For those who are very desperate can type "if True:" on the top of the cells which you want to hide. Then u can fold them. It is surely not very efficient but it will serve the purpose for the time being. 😉

[rchiodo]

@PrateekArya not sure what you are wondering what I'm joking about? Submitting PRs? External contributors have done a bunch of work in the past. Collapsable regions is not high on our backlog at the moment but if somebody else really wants it, we would certainly love any submission.

I believe the solution to this request would be to add a FoldingRangeProvider:
https://code.visualstudio.com/api/references/vscode-api#FoldingRange

In our code where we create code lenses, it probably wouldn't be too hard to add a folding range provider somewhere there.

[DonJayamanne]

For anyone interested here's a sample implementation (created for folding of docstrings).
We'd just need to identify cell markers (we have code for that too - to get the cell ranges).
We're happy to help anyone who wants to take a stab at this.

https://github.com/microsoft/vscode-python/blob/7c81cfcd06cdbfd91224489864ac3c9ae2c16d59/src/client/providers/docStringFoldingProvider.ts#L1-L2

[Diogo-Rossi]

@PrateekArya

For those who are very desperate can type "if True:" on the top of the cells which you want to hide. Then u can fold them. It is surely not very efficient but it will serve the purpose for the time being. 😉

I think it is better to use the region/endregion comment approach, which is somehow official.
Use if True: may lead to indentation erros in some cases . . .

Sorry, I really thought this issue was easy to provide (replacing region/endregion for two %% in sequence)

[pythlang]

Temp comment bump for now as I've just stumbled across this while working and also desire this... I may be able to take a stab at this in a few weeks here with some guidance while I have some free time.

Let me get back to this comment later.