I agree, we have to start using null check for generic value.
Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sat, Jun 18, 2016 at 11:16 AM, Devanshu Vyas < devanshu.v...@hotwaxsystems.com> wrote: > Completely makes sense. > > +1 > > > -- > Thanks and Regards, > Devanshu Vyas > > HotWax Systems > *https://www.hotwaxsystems.com <https://www.hotwaxsystems.com>* > > On Fri, Jun 17, 2016 at 8:00 PM, Ratnesh Upadhyay < > upadhyay.ratn...@gmail.com> wrote: > > > Hello community, > > > > There are lots of places in code where we have used > > UtilValidate.isNotEmpty() or UtilValidate.isEmpty() for GenericValue > object > > . GenericValue is never empty. Its always null or not null. So should we > > use directly null or not null check instead of UtilValidate.isNotEmpty() > > and UtilValidate.isEmpty() for GenericValue objects ? > > > > Basically these validation methods should preferably be used on Strings > or > > Lists and normal Maps. > > > > Thanks!! > > > > Regards, > > Ratnesh Upadhyay > > HotWax Systems | www.hotwaxsystems.com > > >
