Currently folding only happens when the caret is within the block that will be folded (i.e describe('<message>', it('<message>' and so on).
This means that if you have your caret on the intent of a block, folding won't be triggered.
See this gif for an example:
In particular, note where the caret is when the //#region tag folds, vs when folding takes place for the describe block.
Ideally we'd like to match the behaviour of other foldables as much as possible.
I suspect this behaviour actually might be a result of some "fold-up" logic, where IntelliJ looks for the next/closest element to fold when requested to fold, which for some reason our folds don't meet.
This folding happens with other foldables as well, such as class methods:
Currently folding only happens when the caret is within the block that will be folded (i.e
describe('<message>',it('<message>'and so on).This means that if you have your caret on the intent of a block, folding won't be triggered.
See this gif for an example:
In particular, note where the caret is when the
//#regiontag folds, vs when folding takes place for thedescribeblock.Ideally we'd like to match the behaviour of other foldables as much as possible.
I suspect this behaviour actually might be a result of some "fold-up" logic, where IntelliJ looks for the next/closest element to fold when requested to fold, which for some reason our folds don't meet.
This folding happens with other foldables as well, such as class methods: