Description
Currently, we have different validations scattered around the methods that accept a single String argument such as inNamespace, withName, and so on.
We should be consistent and perform the same validation across the code-base. Ideally an Utils.isNotBlank method should be used for null, 0-length, or blank String check.
It can be - but we aren't doing that check with the other inNamespace, or other string name, locations. Ideally we would be consistent about not accepting empty / null anywhere a name was expected - so maybe a separate issue to cover that.
Originally posted by @shawkins in #4027 (comment)
Description
Currently, we have different validations scattered around the methods that accept a single String argument such as inNamespace, withName, and so on.
We should be consistent and perform the same validation across the code-base. Ideally an Utils.isNotBlank method should be used for null, 0-length, or blank String check.
It can be - but we aren't doing that check with the other inNamespace, or other string name, locations. Ideally we would be consistent about not accepting empty / null anywhere a name was expected - so maybe a separate issue to cover that.
Originally posted by @shawkins in #4027 (comment)