handling commas and dots input in parseToken of Parser

[naronchen]

#7487

Right now I have any input consists only special characters returning a parseError or a quantity with isValid field being false.

this should be all the special characters.
/^[!@#$%^&*()_+-=[]{};':"\|,.<>/?]+$/;

Let me know if thats expected, or we wanna handle just the dots/comas occurrences

[hl662]

@mathieu-fournier I'll let you chime in on whether we should check only commas and dots, or check all special characters (and if the special characters mentioned are enough or we missing any)

[naronchen]

Just pushed a slightly different fix because Mathieu asked to handle multiple dots and comas mixed into numbers
Now I got these tests cases returning parseError.UnableToConvertParseTokensToQuantity

      "10..",
      "1.2,,3..4...7",
      ",,3..",
      "12..34",
      "1.2.3",
      "..10",
      "1...2",
      "1..",
      "1..,",
      "10,20,30..40",
      "1..e2",
      "1e..2",
      "1e2..",
      "1...2e3",
      "1e2..,3",

the ones with comas is a bit tricky

     "1,,2", // returns 12
     "1.,2", // returns 1.2

the parsing skips comas because the parsing method thinks its a thousands separator so it ignores it, will look into it more.