npm install react-querybuilder --save
OR
yarn add react-querybuilder
OR
To run the demo yourself, go through the following steps:
npm install
Install npm packagesnpm start
Run a local server- http://localhost:8080/ Visit your localhost in your browser
import QueryBuilder from 'react-querybuilder';
const fields = [
{ name: 'firstName', label: 'First Name' },
{ name: 'lastName', label: 'Last Name' },
{ name: 'age', label: 'Age' },
{ name: 'address', label: 'Address' },
{ name: 'phone', label: 'Phone' },
{ name: 'email', label: 'Email' },
{ name: 'twitter', label: 'Twitter' },
{ name: 'isDev', label: 'Is a Developer?', value: false }
];
const dom = <QueryBuilder fields={fields} onQueryChange={logQuery} />;
function logQuery(query) {
console.log(query);
}
The default export of this library is the <QueryBuilder />
React component. Named exports include the <Rule />
component (for use in custom <RuleGroup />
implementations) and a utility function, formatQuery
.
<QueryBuilder />
supports the following properties:
{id?: string, combinator: string, rules: ({field: string, value: any, operator: string} | {rules: ...[], combinator: string})[]}
The initial query, in JSON form (follows the same format as the parameter passed to the onQueryChange
callback). id
is optional. See the demo source for examples.
{name: string, label: string, id?: string}[]
The array of fields that should be used. Each field should be an object with at least:
{name: string, label: string}
The id
is optional. If you do not provide an id
for a field then the name
will be used.
Field objects can also contain other data. Each field object will be passed to the appropriate OperatorSelector
and ValueEditor
components as fieldData
(see the section on controlElements
).
{name: string, label: string}[]
The array of operators that should be used. The default operators include:
[
{ name: 'null', label: 'is null' },
{ name: 'notNull', label: 'is not null' },
{ name: 'in', label: 'in' },
{ name: 'notIn', label: 'not in' },
{ name: '=', label: '=' },
{ name: '!=', label: '!=' },
{ name: '<', label: '<' },
{ name: '>', label: '>' },
{ name: '<=', label: '<=' },
{ name: '>=', label: '>=' },
{ name: 'contains', label: 'contains' },
{ name: 'beginsWith', label: 'begins with' },
{ name: 'endsWith', label: 'ends with' },
{ name: 'doesNotContain', label: 'does not contain' },
{ name: 'doesNotBeginWith', label: 'does not begin with' },
{ name: 'doesNotEndWith', label: 'does not end with' }
];
{name: string, label: string}[]
The array of combinators that should be used for RuleGroups. The default set includes:
[
{ name: 'and', label: 'AND' },
{ name: 'or', label: 'OR' }
];
PropTypes.shape({
addGroupAction: PropTypes.func, // returns ReactClass
removeGroupAction: PropTypes.func, // returns ReactClass
addRuleAction: PropTypes.func, // returns ReactClass
removeRuleAction: PropTypes.func, // returns ReactClass
combinatorSelector: PropTypes.func, // returns ReactClass
fieldSelector: PropTypes.func, // returns ReactClass
operatorSelector: PropTypes.func, // returns ReactClass
valueEditor: PropTypes.func, // returns ReactClass
notToggle: PropTypes.func, // returns ReactClass
ruleGroup: PropTypes.func, // returns ReactClass
rule: PropTypes.func // returns ReactClass
});
This is a custom controls object that allows you to override the control elements used. The following control overrides are supported:
addGroupAction
: By default a<button />
is used. The following props are passed:
{
label: PropTypes.string, // "+Group"
className: PropTypes.string, // CSS classNames to be applied
handleOnClick: PropTypes.func, // Callback function to invoke adding a <RuleGroup />
rules: PropTypes.array, // Provides the number of rules already present for this group,
level: PropTypes.number // The level of the current group
}
removeGroupAction
: By default a<button />
is used. The following props are passed:
{
label: PropTypes.string, // "x"
className: PropTypes.string, // CSS classNames to be applied
handleOnClick: PropTypes.func, // Callback function to invoke removing a <RuleGroup />
rules: PropTypes.array, // Provides the number of rules already present for this group,
level: PropTypes.number // The level of the current group
}
addRuleAction
: By default a<button />
is used. The following props are passed:
{
label: PropTypes.string, // "+Rule"
className: PropTypes.string, // CSS classNames to be applied
handleOnClick: PropTypes.func, // Callback function to invoke adding a <Rule />
rules: PropTypes.array, // Provides the number of rules already present for this group,
level: PropTypes.number // The level of the current group
}
removeRuleAction
: By default a<button />
is used. The following props are passed:
{
label: PropTypes.string, // "x"
className: PropTypes.string, // CSS classNames to be applied
handleOnClick: PropTypes.func, // Callback function to invoke removing a <Rule />
level: PropTypes.number // The level of the current group
}
combinatorSelector
: By default a<select />
is used. The following props are passed:
{
options: PropTypes.array.isRequired, // Same as 'combinators' passed into QueryBuilder
value: PropTypes.string, // Selected combinator from the existing query representation, if any
className: PropTypes.string, // CSS classNames to be applied
handleOnChange: PropTypes.func, // Callback function to update query representation
rules: PropTypes.array, // Provides the number of rules already present for this group
level: PropTypes.number // The level of the current group
}
fieldSelector
: By default a<select />
is used. The following props are passed:
{
options: PropTypes.array.isRequired, // Same as 'fields' passed into QueryBuilder
value: PropTypes.string, // Selected field from the existing query representation, if any
operator: PropTypes.string, // Selected operator from the existing query representation, if any
className: PropTypes.string, // CSS classNames to be applied
handleOnChange: PropTypes.func, // Callback function to update query representation
level: PropTypes.number // The level the group this rule belongs to
}
operatorSelector
: By default a<select />
is used. The following props are passed:
{
field: PropTypes.string, // Field name corresponding to this Rule
fieldData: PropTypes.object, // The entire object from the fields array for this field
options: PropTypes.array.isRequired, // Return value of getOperators(field)
value: PropTypes.string, // Selected operator from the existing query representation, if any
className: PropTypes.string, // CSS classNames to be applied
handleOnChange: PropTypes.func, // Callback function to update query representation
level: PropTypes.number // The level the group this rule belongs to
}
valueEditor
: By default an<input type="text" />
is used. The following props are passed:
{
field: PropTypes.string, // Field name corresponding to this Rule
fieldData: PropTypes.object, // The entire object from the fields array for this field
operator: PropTypes.string, // Operator name corresponding to this Rule
value: PropTypes.string, // Value from the existing query representation, if any
handleOnChange: PropTypes.func, // Callback function to update the query representation
type: PropTypes.oneOf(['text', 'select', 'checkbox', 'radio']), // Type of editor to be displayed
inputType: PropTypes.string, // Type of <input> if `type` is "text"
values: PropTypes.arrayOf(PropTypes.object), //
level: PropTypes.number, // The level the group this rule belongs to
className: PropTypes.string, // CSS classNames to be applied
}
notToggle
: By default,<label><input type="checkbox" />Not</label>
is used. The following props are passed:
{
checked: PropTypes.bool, // Whether the input should be checked or not
handleOnChange: PropTypes.func, // Callback function to update the query representation
title: PropTypes.string, // Tooltip for the label
level: PropTypes.number, // The level of the group
className: PropTypes.string, // CSS classNames to be applied
}
ruleGroup
: By default,<RuleGroup />
is used. The following props are passed:
{
id: PropTypes.string,
parentId: PropTypes.string,
combinator: PropTypes.string,
rules: PropTypes.array,
translations: PropTypes.object,
schema: PropTypes.object,
not: PropTypes.boolean
}
rule
: By default,<Rule />
is used. The following props are passed:
{
id: PropTypes.string,
parentId: PropTypes.string,
field: PropTypes.string,
value: PropTypes.any,
operator: PropTypes.string,
translations: PropTypes.object,
schema: PropTypes.object
}
function(field: string): []
This is a callback function invoked to get the list of allowed operators for the given field.
function(field: string, operator: string): string
This is a callback function invoked to get the type of ValueEditor
for the given field and operator. Allowed values are "text"
(the default), "select"
, "checkbox"
, and "radio"
.
function(field: string, operator: string): string
This is a callback function invoked to get the type
of <input />
for the given field and operator (only applicable when getValueEditorType
returns "text"
or a falsy value). If no function is provided, "text"
is used as the default.
function(field: string, operator: string): []
This is a callback function invoked to get the list of allowed values for the given field and operator (only applicable when getValueEditorType
returns "select"
or "radio"
). If no function is provided, an empty array is used as the default.
function(queryJSON: RuleGroup): void
This is a notification that is invoked anytime the query configuration changes. The query is provided as a JSON structure, as shown below:
{
"combinator": "and",
"not": false,
"rules": [
{
"field": "firstName",
"operator": "null",
"value": ""
},
{
"field": "lastName",
"operator": "null",
"value": ""
},
{
"combinator": "and",
"rules": [
{
"field": "age",
"operator": ">",
"value": "30"
}
]
}
]
}
This can be used to assign specific CSS
classes to various controls that are created by the <QueryBuilder />
. This is an object with the following properties:
{
queryBuilder: string, // Root <div> element
ruleGroup: string, // <div> containing the RuleGroup
header: string, // <div> containing the RuleGroup header controls
combinators: string, // <select> control for combinators
addRule: string, // <button> to add a Rule
addGroup: string, // <button> to add a RuleGroup
removeGroup: string, // <button> to remove a RuleGroup
notToggle: string, // <label> on the "not" toggle
rule: string, // <div> containing the Rule
fields: string, // <select> control for fields
operators: string, // <select> control for operators
value: string, // <input> for the field value
removeRule: string // <button> to remove a Rule
}
This can be used to override translatable texts applied to various controls that are created by the <QueryBuilder />
. This is an object with the following properties:
{
fields: {
title: "Fields",
},
operators: {
title: "Operators",
},
value: {
title: "Value",
},
removeRule: {
label: "x",
title: "Remove rule",
},
removeGroup: {
label: "x",
title: "Remove group",
},
addRule: {
label: "+Rule",
title: "Add rule",
},
addGroup: {
label: "+Group",
title: "Add group",
},
combinators: {
title: "Combinators",
},
notToggle: {
title: "Invert this group",
}
}
boolean
Pass true
to show the combinators (and/or) between rules and rule groups instead of at the top of rule groups. This can make some queries easier to understand as it encourages a more natural style of reading.
boolean
Pass true
to show the "Not" toggle switch for each rule group.
boolean
Pass false
not to reset operator and value for field change.
boolean
Pass true
to reset value on operator change.
formatQuery
formats a given query in either SQL, parameterized SQL, JSON, or JSON without IDs (which can be useful if you need to serialize the rules). Example:
import { formatQuery } from 'react-querybuilder';
const query = {
id: 'g-b6SQ6WCcup8e37xhydwHE',
rules: [
{
id: 'r-zITQOjVEWlsU1fncraSNn',
field: 'firstName',
value: 'Steve',
operator: '='
},
{
id: 'r-zVx7ARNak3TCZNFHkwMG2',
field: 'lastName',
value: 'Vai',
operator: '='
}
],
combinator: 'and',
not: false
};
console.log(formatQuery(query, 'sql')); // '(firstName = "Steve" and lastName = "Vai")'
console.log(formatQuery(query, 'parameterized')); // { sql: "(firstName = ? and lastName = ?)", params: ["Steve", "Vai"] }
An options
object can be passed as the second argument instead of a format string in order to have more detailed control over the output. The options object takes the following form:
interface FormatQueryOptions {
format: 'sql' | 'json' | 'json_without_ids' | 'parameterized'; // same as passing a `format` string instead of an options object
valueProcessor: (field: string, operator: string, value: any) => string; // see below for an example
quoteFieldNamesWith: string; // e.g. "`" to quote field names with backticks (useful if your field names have spaces)
}
For example, if you need to control the way the value portion of the output is processed, you can specify a custom valueProcessor
(only applicable for format: "sql"
).
const query = {
id: 'g-J5GsbcFmZ6xOJCLPPKIfE',
rules: [
{
id: 'r-KneYcwIPPHDGSogtKhG4g',
field: 'instrument',
value: ['Guitar', 'Vocals'],
operator: 'in'
},
{
id: 'r-wz6AkZbzSyDYbPk1AxgvO',
field: 'lastName',
value: 'Vai',
operator: '='
}
],
combinator: 'and',
not: false
};
const valueProcessor = (field, operator, value) => {
if (operator === 'in') {
// Assuming `value` is an array, such as from a multi-select
return `(${value.map((v) => `"${v.trim()}"`).join(',')})`;
} else {
return `"${value}"`;
}
};
console.log(formatQuery(query, { format: 'sql', valueProcessor })); // '(instrument in ("Guitar","Vocals") and lastName = "Vai")'
The 'json_without_ids' format will return the same query without the IDs. This can be useful, for example, if you need to save the query to the URL so that it becomes bookmarkable:
const query = {
id: 'g-J5GsbcFmZ6xOJCLPPKIfE',
rules: [
{
id: 'r-KneYcwIPPHDGSogtKhG4g',
field: 'instrument',
value: ['Guitar', 'Vocals'],
operator: 'in'
},
{
id: 'r-wz6AkZbzSyDYbPk1AxgvO',
field: 'lastName',
value: 'Vai',
operator: '='
}
],
combinator: 'and',
not: false
};
console.log(formatQuery(query, 'json_without_ids'));
// {
// rules: [
// {
// field: 'instrument',
// value: ['Guitar', 'Vocals'],
// operator: 'in'
// },
// {
// field: 'lastName',
// value: 'Vai',
// operator: '='
// }
// ],
// combinator: 'and',
// not: false
// };
In order to use this library with IE11, you must copy the Microsoft-prefixed crypto
implementation to window.crypto
:
if (!window.crypto) {
window.crypto = window.msCrypto
}
This requirement is due to the inclusion of the nanoid
library.
We are using github-changes to generate the changelog.
To use it:
- tag your commit using semantic versioning
- run
npm run generate-changelog
- enter your github credentials at the prompt
- commit
- push your commit and tags
This component was inspired by prior work from: