| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Hold | +1 |
// gopls now offers folding for each block stmt, in if-else statements,
// each block will get its own folding range.
// because go forces to put the close bracket with else like '} else {' or '} else if cond {'
// the offered folding ranges have an overlapping place between the end of if block and the start of else block.
// in vscode now, if the folding ranges have overlapping places, the later one will be ignored,
// so users can only fold the if block and cannot fold the else block.
//
// The workaround adjusts the end position of a if block stmt from Rbrace to the end of the last statement in the block,
// so folding ranges do not have overlapping places.
// note that a single if block stmt isn't necessarily required this logic, but for simplicity,
// we apply this logic to all block stmts inside an if statement.Can you describe the expected behavior of FoldingRange, from first principles, as if for the user manual? Unless I'm missing something, I feel like we ought to be able to specify the entire behavior in fewer words than this.
Gopls seems to produce sensible information in the scenario of interest, so I suspect the problem is on the client side. Let's come to a consensus on the problem in the issue tracker before we attempt a fix.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |