_print_mismatch in relic.core.errors.py does not check for None explicitly

MAK-Relic-Tool / Issue-Tracker

Central Bug Tracker / Issues Board for the MAK Relic Tool

0 stars 0 forks source link

_print_mismatch in relic.core.errors.py does not check for None explicitly #10

Closed ModernMAK closed 2 years ago

ModernMAK commented 2 years ago

This means values which are 'falsy' will affect how the error message prints out;

E.G. MismatchError("Message",1, 0) MismatchError("Message",1, None) MismatchError("Message",1) All produce the same error message, where as the first message should specify an expected value of 0.