tiger_lib::report

Module errors

Source
Expand description

Collect error reports and then write them out.

Structs§

Statics§

Functions§

  • Record a DLC directory from the vanilla installation. label is what it should be called in the error reports.
  • Record a secondary mod to be loaded before the one being validated. label is what it should be called in the error reports; ideally only a few characters long.
  • Disable color in the output.
  • Print all the stored reports to the error output. Set json if they should be printed as a JSON array. Otherwise they are printed in the default output format.
  • Store an error report to be emitted when emit_reports is called.
  • Expand PointedMessage recursively. That is; for the given PointedMessage, follow its location’s link until such link is no longer available, adding a newly created PointedMessage to the given Vec for each linked location.
  • Configure the error reports to be written to this file instead of to stdout.
  • Override the default OutputStyle. (Controls ansi colors)
  • Configure the error reporter to only show errors that match this FilterRule.
  • Configure the error reporter to show errors that are in extra loaded mods. Normally those are filtered out, to only show errors that involve the mod’s code.
  • Configure the error reporter to show errors that are in the base game code. Normally those are filtered out, to only show errors that involve the mod’s code.
  • Extract the stored reports, sort them, and return them as a vector of LogReport. The stored reports will be left empty.
  • Immediately log a single-line report about this error.
  • Immediately print an error message. It is intended to introduce a following block of messages printed with warn_abbreviated.
  • Tests whether the report might be printed. If false, the report will definitely not be printed.