Feature request: Start one block per line about vscode-blockman HOT 5 CLOSED

This looks much better

So actually, this is also a tool to help fix bad formatting. Make the blocks happy and make devs without blocks happy too.

from vscode-blockman.

I don't see any issues here. What do you mean only one block is needed ?

You have turned on analyzing square brackets. Maybe you could turn it off and keep only analyzing curly brackets turned on. So, the blocks won't be too overloaded. But anyway, the blocks are rendering correctly as I see in the image.

from vscode-blockman.

On the top left before 'issued_date', the the purple bracket starts a block instead of the purple curly brace after function, which would correspond with the end of the block. In this situation it would seem more logical to me to use the yellow bracket and the if statement for a block. Right now it looks a bit inconsistent starting at the second bracket and ending at the last curly brace.

The purple bracket is a single line statement and the function curly brace I believe may be skipped because it starts and ends on the same line as the yellow bracket, so the block could start one column earlier and take up the whole line that has the closing bracket and brace.

from vscode-blockman.

No, the start indicator of the block is not the purple bracket. The start indicator is the yellow bracket. You can test it, just write anything between the yellow and the purple brackets, for example a comment like this: /*commnet*/.

And also, the end indicator of the block is not the last curly bracket. It's the last yellow square bracket. You can test it, just write /*commnet*/ between them.

from vscode-blockman.

Ah I see, it looks like that because there is no newline after the yellow bracket. It seems to me that a block is only needed when a newline follows a block token, but that may not work for all code bases.

Prettier would have probably added a newline after the yellow bracket, after the comma before function and after the last curly brace so it seems to be mostly down to bad formatting here.

from vscode-blockman.