Releases: adamhl8/filterql
Releases · adamhl8/filterql
3.0.2
3.0.1
3.0.0
Breaking Changes
- To make the
FilterQL
API more flexible and clear, thefilter
method had been renamed toquery
- Change any calls of the
filter
method toquery
- Change any calls of the
Minor Changes
- Added the
parse
,applyFilter
, andapplyOperations
methods to theFilterQL
class- These may be useful in cases where you want to filter and apply operations separately
Patch Changes
- Added a more explicit check for non-comparable data values to handle some rare cases where a comparison would match when it shouldn't have
2.0.2
2.0.1
Breaking Changes
- Queries are now whitespace-delimited. Previously, a query like
title==Matrix
was valid. Now it must betitle == Matrix
.- As a result, there are no longer restrictions on what characters can be used in fields or values (values containing whitespace must still be quoted).
- The
FilterQL
constructor now takes in oneFilterQLArguments
argument. Instead ofnew FilterQL(schema, options?)
, usenew FilterQL({ schema, options?, customOperations? })
.
New Features
- Queries can now contain operations, which can be used to transform the data after filtering.
- The
*
character can be used in place of a comparison to match all entries.
1.3.1
1.3.0
- Added explicit checks for ambiguous syntax in queries using case-insensitive comparisons
- Now case-insensitive operators must be preceded by whitespace or an error will be thrown
- For example: say you have a query like
ends-in-i==value
. Is thisends-in-i == value
orends-in- i== value
?
1.2.0
- Removed
1
,yes
,y
,0
,no
,n
as valid boolean values - Renamed the
ignoreUnknownFields
option toallowUnknownFields
- When
true
, instead of always matching, the value is compared as normal
- When
- Added proper handling for some edge cases related to
undefined
/null
comparisons