
Not technically 100% correct since null != "null", but without sacrficing performance this is the best way to fix the issue in the current implementation.
Not technically 100% correct since null != "null", but without sacrficing performance this is the best way to fix the issue in the current implementation.