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
unless you set "existingBetweenFields": "remove" current behaviour of formatter is to keep just one empty line between fields and that will beat any of the other settings.
your current sample would work if you removed all empty lines between fields from input. problem is: next formatter run will reduce all double empty lines to just one, because of keep setting.
keep option probably should count number of empty lines in input to add correct amount of empty lines to output.
Thanks for your hints! when I set existingBetweenFields to remove it actually works. It however feels very counter intuitive. I feel like the name and values of that option are misleading. Also, even though it is called existingBetweenFields it also affects empty lines between functions.
Unfortunately when setting existingBetweenFields to remove, as the name implies, all empty lines between fields are removed. So I cannot have something like
Also, even though it is called existingBetweenFields it also affects empty lines between functions.
functions are fields.
Unfortunately when setting existingBetweenFields to remove, as the name implies, all empty lines between fields are removed.
yeah, that is the downside of remove, you can't have custom empty lines to separate different groups of fields. that's why keep is default. it needs a overhaul to support more than one empty line between fields.
Describe the bug
Setting any of the following emptyLines/classEmptyLines options to insert/keep two lines instead of one are ignored by the formatter:
Input file
Broken output
Expected output
Optional: hxformat.json
The text was updated successfully, but these errors were encountered: