Avoid space sanitizing

[entusiastaIA]

This is something that's been bothering me since countless versions ago. For a code like this:

"[if _not angle="back"] and [get faceused][/if];"
Is there anyway to avoid that first space before the "and" to get sanitized and removed. Honestly I don't understand why is it done that way, I write spaces where I need them. Actually this is the workaround code I need to use to fix that which is much less elegant IMO...
"[if angle="back"];[/if] [if _not angle="back"]and [get faceused];[/if]" now the needed space is in between those ifs so that it is parsed...

I have tried with the config file but either I'm not understanding the sanitizing options provided or I cannot fix it.

(I know another option would be adding the space BEFORE the [IF]... the problem with that is that then in case of angle="back" you end with "word ; word" and I know that from the SD perspective it is the same as "word; word" but I refuse to live into such a world of anarchy, chaos and slaughter. I love clean prompts. More than clean code ^^).

PS: I don't use [else] because of the old "why else is true?" that used to happen :)

[ThereforeGames]

Hi @entusiastaIA,

I have added the new setting Config.syntax.cleanup_extra_spaces in Unprompted v10.3.0 - try setting it to false and the leading space in your example should be preserved.

Please note that disabling the space sanitization may cause compatibility issues with other templates or some shortcodes.

[entusiastaIA]

Yes! It's working! First problem/bug I notice now though is with [choose _weighted]:
"[choose _weighted]
3|
1|from the front
[/choose]".
If you leave the area next to the 3 really empty, then the array it builds is "3|1|from the front".

Previously I used an space to fix that behaivour and get the array "3| |1|from the front". Which seems that after sanitizing got really empty. Now however it ends producing an extra space.
I think sanitizing the space is not the way to go, but it was instead a workaround, I think it should be able to build the array "3||1|from the front", and understand the second index as void... But if you think it is not worth the trouble of fixing it I can just revert to my old workarounds.