soql-parser-js - npm Package Versions

2.5.2

April 23, 2020

1. Added support for dates formatted with nanoseconds, such as 2020-04-15T02:40:03.000+0000. (#102)
2. Added support for aggregate function in the ORDER BY clause (#103)
3. Queries would not be properly composed if an order by had a function and also specified ASC or DESC (#104)

2.5.1

April 23, 2020

1. Queries with date functions in a WHERE clause would throw an error when parsing. (#100)

2.5.0

April 3, 2020

1. Passing in null or undefined to compose query no longer throws an exception, but instead returns an empty string. (#95)
2. Regular fields in a select clause now allow aliases because this is allowed if the field is used as part of a group by clause. (#97)
3. getFlattenedFields() now considers if a relationship field was used as part of a group by, and if so it returns just the field name instead of the entire field path, as this is how Salesforce will return the records. (#98)

2.4.1

Mar 22, 2020

1. Updated dependencies to resolve known security vulnerabilities.

2.4

Feb 25, 2020

1. Date literals were not properly parsed if they were included as part of a SET within a WHERE clause, such as WHERE IN (TODAY, LAST_N_DAYS:5).
   1. As part of this change, the dateLiteralVariable property in the Condition will be an array if a variable date literal is included in a SET where clause. Refer to test cases 93 through 98 for examples

2.3.0

Jan 13, 2020

1. The DESC operator in the ORDER BY clause was treated as a case-sensitive field.
2. The following fields we treated as case-sensitive:
   1. NEXT_N_FISCAL_QUARTERS, LAST_N_FISCAL_QUARTERS, N_FISCAL_QUARTERS_AGO, NEXT_N_FISCAL_YEARS, LAST_N_FISCAL_YEARS,
   2. mi, km on GEOLOCATION functions
3. Updated the DISTANCE function to properly be tagged as isAggregateFn=true if used as a field
   1. This fixed an issue where getFlattenedFields() would throw an exception

2.2.3

Jan 4, 2020

1. Added logo to README and updated docs.

2.2.2

Dec 2, 2019

1. When composing a query, if an empty OrderBy array was provided, the composed query would still include the ORDER BY clause in the composed query.

2.2.1

Nov 17, 2019

1. GROUP BY did not allow multiple fields to be listed, for example: SELECT BillingState, BillingStreet, COUNT(Id) FROM Account GROUP BY BillingState, BillingStreet would fail to parse.

2.2.0

Nov 6, 2019

1. DISTANCE and GEOLOCATION functions failed to parse when used in a WHERE clauses and ORDER BY clauses.