From 012861322e1207f57c78339a3a1e4ca7a89c3e9b Mon Sep 17 00:00:00 2001
From: Mark Herhold Plugins are used to extend the possibilities of QueryBuilder either by adding new public method or by modifying
default behaviour. Some plugins like Mongo support and SQL support don't require any configuration and are useable as
+ Some plugins like Mongo support and SQL support don't require any configuration and are usable as
long as they are loaded. Other plugins must be manually activated with the You can find bellow the plugins shipped by default with QueryBuilder, with their identifiers. Want to create a new plugin ? Check our developper doc.
+ Want to create a new plugin ? Check our developer doc.
The MongoDB module requires special configuration of operators to convert rules to a valid Mongo JSON and
- vis-versa. This configuration is stored in the Provides three ways to display a description about a filter: inline, Bootsrap Popover or Bootstrap Popover or Bootbox. The description is defined in the
plugins option. This option
is an object where keys are plugin names and values are plugin configuration (or null).
.setRulesFromMongo(query)Operators
mongoOperators and mongoRuleOperators
+ vice-versa. This configuration is stored in the mongoOperators and mongoRuleOperators
options, the keys are the operators types and the values are formatting functions, see
the source code for more details.
description attribute of each filter. It can contain HTML.