jetstreamapp/soql-parser-js

Issues

• Add support for negative currency values

  #244 opened 5 months ago by paustint
  0

• Invalid JSON for NOT negation when query contains first condtion having NOT Operators

  #242 opened 10 months ago by MirzaHamza00
  2

• Invalid JSON when query contains two consecutive NOT Operators

  #237 opened 10 months ago by MirzaHamza00
  2

• question: are long IN clauses handled?

  #236 opened a year ago by techieshark
  2

• Failed to parse source map

  #227 opened 2 years ago by sylvainar
  8

• Date functions should have isAggregateFn set to true

  #228 opened 2 years ago by paustint
  0

• Format WHERE clause improvement

  #224 opened 2 years ago by paustint
  0

• Invalid NOT query can be parsed without an error while ignoreParseErrors is disabled

  #201 opened 2 years ago by ghingis
  1

• keep literalType in the result JSON

  #207 opened 2 years ago by ghingis
  1

• isNegationOperator does not handle all cases

  #129 opened 4 years ago by paustint
  0

• COMPOSE: Passing in string for value for array operators produces invalid query

  #107 opened 2 years ago by paustint
  0

• Where clause compose query does not handle if properties are undefined

  #121 opened 2 years ago by paustint
  0

• getFlattenedFields returns incorrect results if relationship field is grouped

  #98 opened 5 years ago by paustint
  1

• Group by fields should allow alias

  #97 opened 5 years ago by paustint
  1

• Order by operator is case-sensitive and should not be

  #90 opened 5 years ago by paustint
  1

• typeof query is ignored from getFlattenedFields()

  #115 opened 4 years ago by paustint
  1

• WHERE clause allows and/or as first statement

  #168 opened 2 years ago by paustint
  0

• IDEA: Provide a queryBuilder interface to allow more easily composing queries

  #171 opened 2 years ago by paustint
  0

• Redo docs

  #172 opened 2 years ago by paustint
  7

• Format does not work well with nested negation clauses

  #163 opened 2 years ago by paustint
  0

• Revisit types for where clause

  #128 opened 2 years ago by paustint
  0

• Add WITH USER_MODE and WITH SYSTEM_MODE support

  #193 opened 2 years ago by ghingis
  1

• PROD ISSUE - Parser is incorrectly categorizing value as geolocation unit

  #188 opened 2 years ago by divijklenty
  1

• Add support for partial parse and compose

  #182 opened 3 years ago by paustint
  0

• getFlattenedFields does not work correctly on aliased normal fields

  #160 opened 3 years ago by paustint
  0

• getFlattenedFields does not return accurate resulte when nested aggregate function

  #157 opened 3 years ago by paustint
  0

• Improve apex bind variable parsing

  #155 opened 3 years ago by paustint
  4

• parseQuery fails when bind variable contains parenthesis

  #153 opened 3 years ago by pgonzaleznetwork
  2

• isQueryValid doesn't properly validate SOQL syntax

  #152 opened 3 years ago by pgonzaleznetwork
  4

• GROUP BY does not allow multiple functions

  #149 opened 4 years ago by paustint
  0

• How can I achieve this Identation

  #137 opened 4 years ago by AllanOricil
  7

• Formatting: TYPEOF query should provide better formatting

  #135 opened 4 years ago by paustint
  0

• Add support for FIELDS()

  #136 opened 4 years ago by paustint
  0

• Date functions should be allowed in ORDER BY clause

  #139 opened 4 years ago by 0x17h
  3

• LexingError: unexpected character

  #140 opened 4 years ago by AllanOricil
  6

• getFlattenedFields does not correctly handle alias for grouped expressions

  #131 opened 4 years ago by paustint
  1

• parseQuery not working with FunctionExpressions

  #130 opened 4 years ago by gla5001
  4

• NOT (field expression) fails to parse

  #122 opened 4 years ago by stephen-peck
  8

• QUESTION - Is soql-parser-js case-sensitive regarding some operations on sObjectName ?

  #109 opened 4 years ago by AltiusRupert
  1

• getFlattenedFields returns incorrect results if relationship field is grouped and you are grouping for only one field

  #113 opened 4 years ago by ABenassi87
  0

• Some date formats are not properly parsed

  #102 opened 5 years ago by paustint
  0

• Functions in order by are not composed correctly

  #104 opened 5 years ago by paustint
  0

• Order By does not allow aggregate queries

  #103 opened 5 years ago by paustint
  0

• Date functions should be allowed in where clause

  #100 opened 5 years ago by paustint
  0

• Passing in null or undefined to compose query throws exception

  #95 opened 5 years ago by paustint
  0

• IN clause does not allow date literals

  #92 opened 5 years ago by paustint
  0

• If an empty orderby array is included, the composed query is invalid

  #87 opened 5 years ago by paustint
  0

• Group by does not allow multiple fields

  #85 opened 5 years ago by paustint
  0

• DISTANCE with GEOLOCATION throw errors

  #83 opened 5 years ago by paustint
  0

• getFlattenedFields should allow Query or FieldSubquery or Subquery

  #81 opened 5 years ago by paustint
  0