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
Hi @Andy-Solo thanks for opening a feature request.
I won't have time to work on this in the near future. I'll put an explanation for what I think needs to be done, for either my future self or someone else who might be able to pick it up.
It's hard to tell by reading if that's the spot that matters here, but that's my best guess.
Somehow the parser would need to figure out that the current node is the final flow mapping value, and then optionally emit the comma depending on a yaml_emitter config value. Might be nasty to get working, but perhaps someone other than me will be able to do something easier than what I'm suggesting.
After formatting, the character "," (that is, a comma) appears at the very end before "}":
loop:
- {item_name: doc_tools.plugin, item_path: '{3ACCEF78-860F-4D81-89E5-464C907F3628}'}
- {item_name: QRCode.plugin, item_path: '{D20D0768-6968-482B-8CEB-212D801030CF}'}
- {item_name: randomizer.plugin, item_path: '{2E935B75-113D-4613-BEA0-8879A775A42F}',}
or
The text was updated successfully, but these errors were encountered: