Consistent case for error prefix #104
Labels
chore
Things that need to happen but don't change the behaviour
enhancement
New feature or request
good first issue
Good for newcomers
In error messages the case for writing
error
should be consistent. There seem to be places withERROR:
,Error:
anderror:
in the code. Maybe we should decide for one of those variants and use it consistently.The text was updated successfully, but these errors were encountered: