Ternary operator bug in CardEnumOptions component

[nateplusplus]

While refactoring to TypeScript (#456), I noticed a potential issue within the following snippet:

react-json-schema-form-builder/src/formBuilder/CardEnumOptions.js

Lines 55 to 66 in 58ed4fc

	switch (type) {
	case 'string':
	newVal = ev.target.value;
	break;
	case 'number':
	case 'integer':
	newVal = parseFloat(ev.target.value);
	if (Number.isInteger(newVal))
	newVal = parseInt(ev.target.value, 10);
	if (Number.isNaN(newVal)) newVal = type === 'string' ? '' : 0;
	break;
	default:

On line 64, we know that type is a number or integer, so the ternary condition type === 'string' will never be true. This means if newVal is NaN, it will never be set to an empty string and will always be set to 0. I'm not sure if that is an issue, but wanted to flag this.