Add a parsing test API call #4

  • Enhancment
  • Replied
Assigned to whitetooth3
  • Adirelle created this issue Mar 29, 2009

    What is the enhancement in mind? How should it look and feel?

    Add an API method so calling code could know if a tooltip could not be parsed reliably.

    Please provide any additional information below.

    Addons like RatingBuster could use this call to let the user know the reported numbers may be inaccurate.

  • Adirelle added the tags New Enhancment Mar 29, 2009
  • whitetooth3 posted a comment Mar 31, 2009

    How can LibStatLogic know if the parse is reliable or not? There are strings StatLogic doesn't care about(like OnUse, Procs, SetBonuses), strings that should be parsed but can't, and strings that are parsed incorrectly. LibStatLogic can't really tell the difference between the first two, so I don't know how this can be implemented.

  • whitetooth3 removed a tag New Mar 31, 2009
  • whitetooth3 added a tag Waiting Mar 31, 2009
  • Adirelle posted a comment Apr 2, 2009

    As long as there are only parsed strings and willingly ignored strings, I think it it safe to assume the output should be reliable. In case there are non-parsed and non-ignored strings, telling the user that the information may be inaccurate seems valuable to me.

    At this moment, all stats are reported as if everything has been taken into account, which is not always true. The warning would mean "do not blindly trust the summary about this item, something went wrong".

  • Adirelle removed a tag Waiting Apr 2, 2009
  • Adirelle added a tag Replied Apr 2, 2009

To post a comment, please login or register a new account.