Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade Unit Characteristics trigger #5572

Merged
merged 2 commits into from
Dec 11, 2024
Merged

Conversation

emptyrivers
Copy link
Contributor

very lightly tested, because i don't have a lot of guinea pigs around at this hour

@emptyrivers emptyrivers added the 🎨 Enhancement This pull request implements a new feature. label Dec 8, 2024
WeakAuras/Modernize.lua Outdated Show resolved Hide resolved
It's not impossible for a user to declare that a TSU variable is of type string,
but then actually populate it with something else entirely. Unfortunately,
"TSU variables are trustworthy" is an invariant conditions relies on, so e.g.
a condition to check if a string variable contains a substring would fail
if a joker populated the state variable with a non-string value.

Since Conditions are evaluated on a critical path to opening options, we need to trap any errors
from this kind of shenanigans to allow the user to back out of their foolishness. Simply wrapping
RunConditions in xpcall will possibly lead to half finished property applications, but that is
much preferable to Options bricking up.
@InfusOnWoW InfusOnWoW merged commit 1f0feb8 into WeakAuras:main Dec 11, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎨 Enhancement This pull request implements a new feature.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants