Significant bug in text format handling about ls_ui

[ls-]

Hm, I'll test it a bit later today...

TY for the report <3

[ls-]

Got it.

[ls:power:color] isn't a legit tag, so when you try to use it this error:
1x ...acels_UI\modules\unitframes\units\player-Player.lua:36: Attempted to use invalid tag [ls:power:color].

Technically, it's not a bug, it's the intended behaviour. I may add tag string validation though...

[ls-]

On a side note, you should prob install BugSack and BugGrabber, by default, Blizz lua error reporting is disabled.

[klaxce]

The expected behavior of a malformed tag shouldn’t be to break half of the addon. So anything that stops that would be great. To be fair, I didn’t actually have Lua errors turned on and so it took me a few profile resets to figure out what was causing the addon to break. I hadn’t realized that the tags were static and not dynamically accepting arguments, so I had tried to shorten my tag to set power text and color in one tag.

…

On Aug 12, 2018 at 01:55, <Val Voronov ***@***.***)> wrote: Got it. [ls:power:color] isn't a legit tag, so when you try to use it this error: 1x ...acels_UI\modules\unitframes\units\player-Player.lua:36: Attempted to use invalid tag [ls:power:color]. Technically, it's not a bug, it's the intended behaviour. I may add tag string validation though... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub (https://github.com/ls-/ls_UI/issues/40#issuecomment-412328659), or mute the thread (https://github.com/notifications/unsubscribe-auth/AObmtBioEPcZ7fLB6sAZ2KJb70EOY9iAks5uP-1tgaJpZM4V5ECd).

[ls-]

K, now if you try to use something like this: [ls:health:cur][tag #1] [tag #2], tag setter won't update the string, and you'll see a message like this in the config's status bar: