[Bug] - Extension alters workspace.settings.json with incorrect settings

[Tristimdorion]

When installing the latest pre-release the workspace settings for 'Colors' create faulty settings with garbled data.

[duckdoom4]

Hi there, thanks for the bug report. Could you include a sample of the invalid data?

[duckdoom4]

Please try v2.3.4, this issue is likely fixed in that build :)

[Tristimdorion]

Can confirm issue is resolved with v2.3.4

[Tristimdorion]

Unfortunately, it is back, here is an overview of the faulty settings in my workspace and I think it is related to this line in my renpy code:

menu:
"Light Distraction\n{color=ff0000}{size=18}[distraction_percentages[0]]%% Chance{/size}{/color}"

Hope this helps:

			{
				"scope": "renpy.meta.color.#ffff00",
				"settings": {
					"foreground": "#ffff00"
				}
			},
			{
				"scope": "renpy.meta.color.ff0000",
				"settings": {
					"foreground": "ff0000"
				}
			},
			{
				"scope": "renpy.meta.color.ff0000}{size=18}[distraction_percentages[2]]%% chance{/size}{/color}\":",
				"settings": {
					"foreground": "ff0000}{size=18}[distraction_percentages[2]]%% chance{/size}{/color}\":"
				}
			},
			{
				"scope": "renpy.meta.color.ff0000}{size=18}[distraction_percentages[1]]%% chance{/size}{/color}\":",
				"settings": {
					"foreground": "ff0000}{size=18}[distraction_percentages[1]]%% chance{/size}{/color}\":"
				}
			},
			{
				"scope": "renpy.meta.color.ff0000}{size=18}[distraction_percentages[0]]%% chance{/size}{/color}\":",
				"settings": {
					"foreground": "ff0000}{size=18}[distraction_percentages[0]]%% chance{/size}{/color}\":"
				}
			}

[duckdoom4]

Okay, so I resolved this issue however I'm a little surprised.
The issue is that {color=ff0000} doesn't contain a #. According to the renpy documentation this is invalid syntax. Does it actually compile and work as intended?
If it does work I may need to resolve this in a different way.

[Tristimdorion]

It really does work, it just renders as if the # was there.

[duckdoom4]

Hm, okay. In that case I'll have to add support for that