Closed divijklenty closed 2 years ago
@divijklenty - Thank you for reporting this issue ❤️ and I am VERY surprised this was not identified sooner as this library has been used millions of times in a production application to parse user generated queries and this never creeped up as far as I know.
Version 4.4.1 has been released to resolved this issue.
Description
Parsing a soql query that contains
'MI' or 'KM'
as a value is incorrectly being categorized as a geolocation unit instead of a string literal.Steps -
SELECT State_Abbr_c FROM Contact WHERE State_Abbr_c = 'MI'
MI
token is being categorized as a geolocation unit instead of a string literal which is throwing an error.