CoerceFloat throwing error instead of parsing string to float from json

Hi i notice that recently i started getting this error TypeError: Float cannot represent non numeric value: “234234234” at GraphQLScalarType.coerceFloat [as parseValue] i have another api that works fine when i started looking at the problem i realize that graphql was a different version where in version 14.1.1 coerceFloat is

function`` coerceFloat(value) {
  if (!(0, _isFinite.default)(value)) {
    throw new TypeError("Float cannot represent non numeric value: ".concat((0, _inspect.default)(value)));
  }

  return value;
}

in version 0.13.2 coerceFloat is

function` coerceFloat(value) {
  if (value === '') {
    throw new TypeError('Float cannot represent non numeric value: (empty string)');
  }
  var num = Number(value);
  if (num === num) {
    return num;
  }
  throw new TypeError('Float cannot represent non numeric value: ' + String(value));
}

when i copy paste second one in first one in scalar.js it just works fine

[BePasquet]

@ivanGoncharov Thanks for building things like this for us

[IvanGoncharov]

sorry my ignorance but input type number return strings so all inputs on fe web apps will need to be parsed?

@BePasquet Yes, moreover it’s always a good idea to validate on fe. GraphQL validation is intended to assist with debugging during development that’s why error messages are not user-friendly and don’t support for internationalization.