Closed Peter-Day closed 4 months ago
(some notes for whoever picks this up first: https://discord.com/channels/327414731654692866/327414731654692866/1255413120604700735 TL;DR some silly changes from blizzard mean we need to manually add ColorMixin to the custom code fenv in a rawget
able way)
This should work now, we've added a workaround for blizzard's bug to the latest alpha.
Also reported to blizzard via https://github.com/Stanzilla/WoWUIBugs/issues/589
Though I have very little hope that they'll fix it.
Thank you for adding this workaround! Everything's working fine now.
What was the work-around? I'm having the same issue with Vector2DMixin not being found when calling C_AreaPoiInfo.GetAreaPOIInfo() after setfenv was used. I had to add Vector2DMixin directly to function environment but seems counterproductive as these types of problems can pop up at any time with any function and would be difficult to notice without user reports.
See the linked pull requests for my best guess on what the problem is.
Is there an existing issue for this?
Description
Found someone else who had a similar issue in the pull request thread for the initial TWW alpha version, but I realized this bug might have gotten lost there, so posting a separate bug report for it.
Some wow api functions, when called inside of a weakaura script, will give the error in the title: "unable to find mixin (ColorMixin)"
I found this bug trying to use C_ChallengeMode.GetKeystoneLevelRarityColor. The other comment was using C_TooltipInfo.GetHyperlink. See: https://github.com/WeakAuras/WeakAuras2/pull/5071#issuecomment-2133352503
Of course, there are likely many others.
WeakAuras Version
WeakAuras 5.14.1
World of Warcraft Flavor
Beta (WoW 11.0)
World of Warcraft Region
US/NA
Tested with only WeakAuras
I got this issue with only WeakAuras enabled
Lua Error
Reproduction Steps
Create a WeakAura. In the OnInit, add
local test = C_ChallengeMode.GetKeystoneLevelRarityColor(5)
Last Good Version
No response
Screenshots
No response
Export String
Bisector Report
No response