@react-querybuilder/chakra - npm Package Versions

[v6.5.4] - 2023-11-04

Fixed

• [#585] Avoid React warning about unique key props.
• [#585] Fixed invalid reference to generatePicker in @react-querybuilder/antd.

[v6.5.3] - 2023-10-20

Added

• [#574] transformQuery enhancements:
  • rules properties are no longer retained unconditionally. The rules property can be copied or renamed like any other property using the propertyMap option.
  • propertyMap keys can now have false values. Properties matching a propertyMap key with a value of false will be removed without further processing (including the rules property, which would avoid recursion through the hierarchy althogether).
  • New boolean option omitPath. When true, a path property will not be added to each rule and group in the query hierarchy.

Fixed

• paramsKeepPrefix was not applying to bind variables generated from rules with an operator of "between", "notBetween", "in", or "notIn".

[v6.5.2] - 2023-10-19

Changed

• The useValueEditor hook will now update all values that are arrays (Array.isArray(value)) to the first element of the array (value[0]) when operator is anything except "between", "notBetween", "in", or "notIn". Previously this logic only applied when inputType was "number". (To bypass this logic, pass { skipHook: true }.)

Added

• New paramsKeepPrefix option for formatQuery, which enables compatibility with SQLite. When used in conjunction with the "parameterized_named" export format, the params object keys will maintain the paramPrefix string as it appears in the sql string (e.g. { '$param_1': 'val' } instead of { param_1: 'val' }).

Fixed

• [#523] parseMongoDB now properly handles objects in the form of { fieldName: { $not: { /* ...rule */ } } }. This problem was particularly evident for $regex operators that should have generated rules with "doesNot[Contain/BeginWith/EndWith]" operators, since formatQuery(query, 'mongodb') produces this structure and parseMongoDB was not handling the inverse operation.
• isRuleGroup will not error when the argument is null.
• [#572] parseSQL now recognizes signed numeric values like -12 or +14.

[v6.5.1] - 2023-06-26

Fixed

• AntDValueEditor calls generatePicker from the correct import.
• Packages no longer "masquerade as CJS" when imported from ESM under "node16" module resolution.

[v6.5.0] - 2023-06-13

Changed

• [#529] Drag handle components will no longer be rendered unless drag-and-drop is enabled. Previously, drag handle components were rendered unconditionally. Accordingly, the default stylesheet no longer applies display: none to the queryBuilder-dragHandle class when drag-and-drop is disabled since the components will not be rendered anyway.

Added

• [#529] New props for several sub-components:
  • The parent rule object will now be provided to fieldSelector, operatorSelector, valueSourceSelector, and valueEditor components.
  • The parent ruleGroup object will now be provided to notToggle components.
  • The parent ruleOrGroup object will now be provided to dragHandle components.

Fixed

• [#529] The full rule object will now be passed to field-based validator functions. Previously, the parameter object only included the field, operator, valueSource, and value properties of the rule.

[v6.4.1] - 2023-05-23

Fixed

• The custom JsonLogic operators startsWith and endsWith (properties of jsonLogicAdditionalOperators) now check the type of the first parameter before calling the respective methods. This avoids errors like "Uncaught TypeError: Cannot read properties of null (reading 'startsWith')" when a field in the object being evaluated is null.