Filter Deferred XML Node object errors?

[Hekili]

A new issue in BfA (not with your addon, but with WoW itself reporting a previously hidden error) is that some XML-based libraries are very common, found in multiple addons, and will proc errors on every reload reporting that the objects already exist.

It would be really nice if we could have a checkbox option to filter out these harmless errors that there's really no point in seeing anyway. Are you open to blocking those?

[funkydude]

I don't think going down the path of filtering valid errors is going to resolve anything.

The XML errors occur because library authors have incorrectly decided to use XML to create a frame template, instead of using that same library to create a common function that frames can be passed to and have all those attributes set to them.

The only way authors will fix their flawed libraries is with pressure, exact same effect as standard errors have. If I let people filter it they will just say "it's fine just filter it", achieving nothing.

I'm going to leave this open for now, hopefully people will read this instead of continually opening new issues.

[sgkdnay]

4x Deferred XML Node object named Lib_UIDropDownMenuButtonTemplate already exists

I'm getting the same error but question is WHICH addon is causing it? Not enough details to whom we can report to and what addon was making this error

[funkydude]

@sgkdnay In regards to Lib_UIDropDownMenuButtonTemplate please refer to: #8

The error lacking the source of the culprit is something I've asked Blizz to address.

[tymesink]

@funkydude I understand you want the addon author to fix their bugs. So do we all. But sometimes, it takes time to fix a bug due to time availability. I think it would be good for the non-developers to be able to filter out or ignore known bugs that are harmless. Anyhow that's my 2 cents. I really like this addon, I've used it for years.