You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have never been a fan of the empty lines that the formatter adds when formatting my spec-files. Especially the ones added before tables:
I'd like to control that myself. I understand that this might seem like a small thing that only annoys me, but still, can't help but suggest an implementation where one can toggle whether new lines should be added during formatting (around tags, and before tables).
I suggest a flag '--skip-empty-line-insertions' on the format command:
As well as a settings in VSC, since at least I do 99% of formatting in VSC.
Default (if setting is omitted or false) will of course be the "normal" behavior.
I've created the code from the best of abilities (I'm no Go-developer, nor I have understood the gauge implementation in full).
@sriv I would appreciate if you at least look at the PR:
I can understand the argument of not wanting to add complexity for solving a "non-issue", but still ;)
To make it work in VSC a small update for the extension is needed that sends the settings to the Gauge server, (otherwise default behavior will always be used), that code is ready if this would be considered.
The text was updated successfully, but these errors were encountered:
Hi!
I have never been a fan of the empty lines that the formatter adds when formatting my spec-files. Especially the ones added before tables:
I'd like to control that myself. I understand that this might seem like a small thing that only annoys me, but still, can't help but suggest an implementation where one can toggle whether new lines should be added during formatting (around tags, and before tables).
I suggest a flag '--skip-empty-line-insertions' on the format command:
As well as a settings in VSC, since at least I do 99% of formatting in VSC.
Default (if setting is omitted or false) will of course be the "normal" behavior.
I've created the code from the best of abilities (I'm no Go-developer, nor I have understood the gauge implementation in full).
@sriv I would appreciate if you at least look at the PR:
#2692
I can understand the argument of not wanting to add complexity for solving a "non-issue", but still ;)
To make it work in VSC a small update for the extension is needed that sends the settings to the Gauge server, (otherwise default behavior will always be used), that code is ready if this would be considered.
The text was updated successfully, but these errors were encountered: