@react-querybuilder/bulma - npm Package Versions

[v5.3.2] - 2022-12-26

Added

• [#434] Added jsonLogicOperations option to parseJsonLogic to enable parsing of custom operations.

[v5.3.1] - 2022-12-23

Fixed

• [#432] The crypto package was used in a way that didn't work in some Node environments.

[v5.3.0] - 2022-12-23

Changed

• New rule and group ids are now generated as valid v4 UUIDs using crypto.getRandomValues() instead of Math.random(). The generateID function used internally is exported.
• [#418] TypeScript interface NameLabelPair has been deprecated and is now an alias for the Option interface.

Fixed

• [#407] Drag-and-drop will now allow drops on locked rules (which places the dragged rule/group below the drop target) and above locked rules/groups.
• [#411] When showCombinatorsBetweenRules is enabled, a combinator selector immediately above a locked rule/group will no longer be locked unless the group it belongs to is locked.
• jsonLogicAdditionalOperators is exported again (documentation).

Added

• [#422] Adding the class queryBuilder-branches displays "tree view" branch lines.
• [#426] Dynamic classnames based on the specific rule/group properties.
  • New function props getRuleClassname and getRuleGroupClassname are passed the rule or group, and the return value will be added as a class to the surrounding div.
  • Field, Operator, and new interface Combinator now have an optional className property that will be applied to rules or groups that specify the appropriate attribute.
• [#417] Optional arity property for operators. When arity is either "unary" or a number less than 2, the value editor will not render when that operator is selected (similar to the standard "null"/"notNull" operators).
• [#408] The interfaces Option (née NameLabelPair), Field, and ValueEditorProps now accept generics for name and other properties.
• [#418] A new OptionList type covers the options property for all standard selection lists (field, operator, combinator, etc.). Previously this was a union type: NameLabelPair[] | OptionGroup<NameLabelPair>[]. OptionList is equivalent to this type, but 1) doesn't require typing the base type twice, and 2) uses the new Option name instead of the deprecated NameLabelPair.
• [#421] When independentCombinators is enabled, custom onAddRule and onAddGroup callbacks can add a combinatorPreceding property to the rule/group which will end up being the combinator inserted above the new rule/group (if the parent group is not empty).

[v5.2.0] - 2022-11-26

Added

• [#403] Add onRemove prop and pass rule/group to all ActionElements (buttons).

[v5.1.3] - 2022-11-23

Fixed

• [#387] Support antd version 5.

[v5.1.2] - 2022-11-21

Fixed

• [#399]/[#401] When dragging a rule or group over a group header, the dndOver class is no longer applied to child group headers.

[v5.1.1] - 2022-10-27

Fixed

• parseMongoDB and parseJsonLogic now respect independentCombinators option.
• Narrowed rule group types, like DefaultRuleGroupType and DefaultRuleGroupTypeIC, are respected by convertFromIC and convertToIC.

<details> <summary>Miscellaneous</summary>

• v3 documentation was migrated from dedicated README to website versioned docs

</details>

[v5.1.0] - 2022-10-26

Fixed

• [#394] parseJsonLogic now handles null values correctly.

Added

• [#392] parseMongoDB utility for importing queries from MongoDB.

[v5.0.0] - 2022-10-22

Changed

• Internet Explorer is no longer supported.
• The minimum TypeScript version is now 4.5.
• When defaultQuery is defined, an id property will be added to each rule and group in the query hierarchy. This will be reflected in the onQueryChange callback parameter. In previous versions defaultQuery was not modified by the component itself, but id is now added because it is a required attribute internally.
• Related to the previous bullet, the prepareRuleGroup utility function will no longer coerce the not property of groups to be a boolean type (or even defined at all).
• [#385] MongoDB output has been simplified: The $eq and $and operators are only used when necessary.
• [#343] Drag-and-drop functionality migrated
  • In order to make the react-dnd dependency completely optional when the enableDragAndDrop prop was not set to true, drag-and-drop functionality was extracted from react-querybuilder into a new package called @react-querybuilder/dnd.
  • The new package has peerDependencies of react-dnd and react-dnd-html5-backend (each of which can be any version >= 14, as long as they match), but no hard dependencies. The only external dependencies in the main package now are immer and clsx.
  • Upgrade path: To enable drag-and-drop functionality in v5, nest <QueryBuilder /> within a <QueryBuilderDnD /> element. The enableDragAndDrop prop is implicitly true when using QueryBuilderDnD, so you no longer need to set it explicitly unless it should be false (which can be set on QueryBuilderDnD or QueryBuilder).

     export function App() {
       return (
    -    <QueryBuilder enableDragAndDrop />
    +    <QueryBuilderDnD>
    +      <QueryBuilder />
    +    </QueryBuilderDnD>
       );
     }
    

  • If your application already uses react-dnd and renders DndProvider higher in the component tree, replace QueryBuilderDnD with QueryBuilderDndWithoutProvider.

Fixed

• [#324] The @react-querybuilder/material package now properly inherits the theme configuration from ancestor ThemeProviders. Note: the @mui/material components are now loaded asynchronously by default, so the query builder will initially be rendered with the default components. See the documentation or the README to find out how to render the MUI components immediately.
• parseCEL now handles strings correctly (including multi-line strings).
• [#389] AntDValueSelector properly handles empty string values in multiselect mode.

Added

• Each compatibility package now exports its own context provider that injects the appropriate controlElements and controlClassnames properties into any descendant QueryBuilder components (composition FTW!). This is now the recommended usage for all compatibility packages.
• The onAddRule and onAddGroup callback props now receive an optional "context" parameter as the fourth argument. This parameter can be provided by a custom addRuleAction/addGroupAction component to its handleOnClick prop. This allows users to alter or replace the default rule based on arbitrary data. For example, the addRuleAction component could render two "add rule" buttons which add different rules depending on which one was clicked, as long as they provided a different context parameter.
• When drag-and-drop is enabled, rules will be copied instead of moved if the user has a modifier key (<kbd>Alt</kbd> on Windows/Linux, <kbd>⌥ Option</kbd> on Mac) pressed when the drop occurs.
• formatQuery has a new ruleProcessor configuration option applicable to non-SQL query language formats. When provided, the entire rule output will be determined by the function. For the relevant formats, valueProcessor already behaved this way; the default "value" processors have been renamed to defaultRuleProcessor[Format] to clarify the behavior. The default processors' original "value" names are deprecated but still available (with no immediate plans to remove them).
• parseSQL will now ignore a leading WHERE keyword, e.g. parseSQL("WHERE firstName = 'Steve'") will not fail to produce a query rule like in v4.

<details> <summary>Miscellaneous</summary>

• The documentation site now has separate documentation for past versions.
• The controlElements prop has a new option: inlineCombinator. By default, this is a small wrapper around the combinatorSelector component that is used when either showCombinatorsBetweenRules or independentCombinators is true. The inlineCombinator option was only added to support @react-querybuilder/dnd, so there is almost certainly no reason to use it directly.

</details>