Replies: 2 comments 4 replies
-
|
Will this be addressed or not?? |
Beta Was this translation helpful? Give feedback.
-
|
Okay, @rtaskf, I dug into this a bit now that I had the time. This is pretty much expected behavior in (If you can point out a version that has acted differently, that'd be very interesting to see!) We strip leading whitespace out of variant members, for one because it makes writing variants out as multiple lines much cleaner. The easy workaround is turning your into since we naturally never strip any whitespace out from literals. If you like, you can turn "Ignore whitespace in prompts" on in the extension settings so there'll be no stray spaces left, but I don't think they affect the end result in any way. Hope this helps, and happy holidays! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
So, after the comma issue was fixed (#672), now it's the white spaces that get removed from the beginning/end of wildcards. This has broken all my files again. Can you please fix that and let the user decide where they want commas and white spaces? I don't see the need to further pre-process the strings. It only makes the system more restrictive and breaks existing "libraries" every time.
I can no longer use something like "{|oil |water }painting{| on the wall}", as it becomes "oilpaintingon the wall" without the "padding".
Beta Was this translation helpful? Give feedback.
All reactions