Not an error code, the message itself. It was testing independently whether a word in the message was upper case or lower case (Does string contains "Something"? Does string contain "something"). It was just a "guess" on what some random 3rd party library might emit as an error message.

There was also no need to catch and re-throw an error with a different message in this context - just let the error happen, nothing was handling it.

Not an error code, the message itself. It was testing independently whether a word in the message was upper case or lower case (Does string contains "Something"? Does string contain "something"). It was just a "guess" on what some random 3rd party library might emit as an error message.

There was also no need to catch and re-throw an error in this context - just let the error happen, nothing was handling it.

Not an error code, the message itself. It was testing independently whether a word in the message was upper case or lower case (Does string contains "Something"? Does string contain "something"). It was just a "guess" on what a 3rd party library might emit as an error message.

There was also no need to catch and re-throw an error in this context - just let the error happen, nothing was handling it.

Not an error code, the message itself. It was testing independently whether the word was upper case or lower case (Does string contains "Something"? Does string contain "something"). It was just a "guess" on what a 3rd party library might emit as an error message.

There was also no need to catch and re-throw an error in this context - just let the error happen, nothing was handling it.