🚀 Big News: Socket Acquires Coana to Bring Reachability Analysis to Every Appsec Team.Learn more
Socket
Book a DemoInstallSign in
Socket

@react-querybuilder/fluent

Package Overview
Dependencies
Maintainers
1
Versions
85
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@react-querybuilder/fluent - npm Package Versions

1
5679

6.2.0-alpha.1

Diff
jakeboone02
published 6.2.0-alpha.1 •
jakeboone02
published 6.2.0-alpha.0 •
jakeboone02
published 6.1.4 •

Changelog

Source

[v6.1.4] - 2023-03-27

Fixed

  • Subpath exports for utility functions (formatQuery, transformQuery, and the parse* functions) now map to their TypeScript types and work for all module resolution strategies.
jakeboone02
published 6.1.3 •

Changelog

Source

[v6.1.3] - 2023-03-24

Fixed

  • [#491] Chakra UI components no longer have hardcoded style-related props like size, variant, and colorScheme.
  • [#491] The schema prop will no longer be passed down to Ant Design and Chakra UI components.
jakeboone02
published 6.1.2 •

Changelog

Source

[v6.1.2] - 2023-03-21

Fixed

  • parseCEL now recognizes dot-separated identifiers correctly.
jakeboone02
published 6.1.1 •
jakeboone02
published 6.1.0 •

Changelog

Source

[v6.1.0] - 2023-03-16

Fixed

  • [#488] The formatQuery option quoteFieldNamesWith now applies to values that represent field names (i.e. valueSource: 'field') when exporting to a SQL-based format.

Added

  • [#488] The formatQuery option ruleProcessor now applies to the "sql" format (though notably not the other SQL-based formats, "parameterized" and "parameterized_named"), allowing complete control over each rule's translation to SQL. The default rule processor for "sql" is exported as defaultRuleProcessorSQL.
jakeboone02
published 6.0.7 •

Changelog

Source

[v6.0.7] - 2023-03-10

Fixed

  • [#486] Custom, non-legacy valueProcessor functions called from formatQuery will now receive all relevant options, not only parseNumbers.
jakeboone02
published 6.0.6 •

Changelog

Source

[v6.0.6] - 2023-03-07

Fixed

  • [#483] The regular expression behind parseSQL in the previous version was capturing too many characters when field names were wrapped in delimiters.
jakeboone02
published 6.0.5 •

Changelog

Source

[v6.0.5] - 2023-03-06

Fixed

  • [#479] parseSQL is now much more permissive of valid characters within strings and identifiers (whether they are delimited or plain). ([#478] only added recognition of spaces within delimited identifiers.)