NgxQueryBuilder

Demo

Stackblitz

Overview

The ngx-query-builder (ngx-qb) is an importable Angular component designed to quickly and easily create a cascading filter for queries or other rule sets. It was modeled after the jQuery QueryBuilder to be a more Angular focused and purpose-built solution.

Sample Usage

Note: Updated for Ng20

import { Component } from '@angular/core';
import { Condition, Filter, IDataField, IElasticFilterGroup, NgxQueryBuilderComponent } from 'ngx-query-builder';

@Component({
  selector: 'ngx-qb-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss'],
  imports: [
    NgxQueryBuilderComponent
  ]
})
export class AppComponent {
  filter: Partial<Filter> = {
    filterLevel: 1,
    id: 1,
    isGroupTF: true,
    clause: 'AND',
    value: null,
    value2: null,
    subFilters: []
  };
  newConditionList: Condition[] = [{
    text: 'Test Condition',
    shortCode: 'tst',
    usedFor: ['string', 'date'],
    usesValue2: true
  }];
  dataFieldList: IDataField[] = [
    {
      text: 'Author',
      type: 'string',
      fieldName: 'author'
    },
    {
      text: 'Title',
      type: 'string',
      fieldName: 'title'
    },
    {
      text: 'Date Published',
      type: 'date',
      fieldName: 'publishedDT'
    },
    {
      text: 'Copies Sold',
      type: 'number',
      fieldName: 'copiesSold'
    }
  ];

  public filterChanged(filter: Filter): void {
    console.log('FC', filter);
  }

  public filterReset(): void {
    console.log('FR');
  }

  public queryExecuted(filterGroup: IElasticFilterGroup): void {
    console.log('QE', filterGroup);
  }

  public maxDepthReached(): void {
    console.log('MDR');
  }
}

<ngx-qb
  [filter]="filter"
  [dataFieldList]="dataFieldList"
  [maxFilterDepth]="0"
  [overrideConditionList]="false"
  [newConditionList]="newConditionList"
  (filterChanged)="filterChanged($event)"
  (filterReset)="filterReset()"
  (queryExecuted)="queryExecuted($event)"
  (maxDepthReached)="maxDepthReached()">
</ngx-qb>

Inputs

| Name | Type | Default | Req. | Description | | --------------------- | ---------------------------- | ------------------------- | -------- | ----------- | | filter | input - Partial<Filter> | Filter.NewTopLevelFilter | False | This is the initial filter passed to the component, if the default is not preferred | | dataFieldList | input - IDataField[] | none | True | Required input for what data fields the query builder should provide the user as options in the first dropdown selector | | resetOnUpdate | input - boolean | false | False | Determines whether resetting a field also resets the properties after that field (dataField => condition => value & value2) | | maxFilterDepth | input - number | 10 | False | Maximum amount of children filters allowed before preventing another layer from being created, provide 0 for infinite depth (will look like trash at around depth 20, depending on screen size) | | overrideConditionList | input - boolean | false | False | If true, the original condition list will be discarded and only the newConditionList will be used | | newConditionList | input - Condition[] | [] | False | List of new conditions for the query builder component to use either in conjunction with or in place of the original condition list | | filterChanged | output - Filter | N/A | N/A | EventEmitter that returns the new value of the filter (Filter) every time a change occurs | | filterDeleted | output - number | N/A | N/A | EventEmitter that returns the value of any deleted filters (internally used) | | filterReset | output - void | N/A | N/A | EventEmitter that returns nothing, merely informs the listener that the filter was reset | | queryExecuted | output - IElasticFilterGroup | N/A | N/A | EventEmitter that returns the value of the entire query filter for API consumption | | maxDepthReached | output - void | N/A | N/A | EventEmitter that informs the user that the max allowable depth has been reached |

You can pass into the <ngx-qb> element an initializing filter, but you must at least pass in a dataFieldList to provide the query builder with dataField options. This is the fully custom list that allows you to specify what fields you will be working with. Without providing your own list, the QueryBuilder component will not do anything. It will still work, it just...well, will have no fields to choose from.

The dataFieldList is the list of all the dataField dropdown options that you want the user to select from in the first dropdown box. The properties of text and fieldName are freeform string options, they can be anything that you'd like. Keep in mind that text is what the user will see, and fieldName is ideally the database column name being referenced, it can however be used however you'd like.

The only restricted field is type, it must be one of the types listed in the IDataField interface: array | string | number | date | boolean | json. Depending on the type, that will determine what fields are displayed for the condition field. Ex: If you use a type of date or number, you can expect such conditions as greater than, less than, between, or not between.

Depending on the condition specified, you can also get up to 2 value boxes. The second box is reserved for conditions requiring 2 values, such as between or not between A and B.

Custom Included Models

Filter

class Filter {
  public static get NewTopLevelFilter(): Partial<Filter> {
    return new Filter({
      filterLevel: 1,
      id: 1,
      isGroupTF: true,
      clause: 'AND',
      value: null,
      value2: null,
      filters: []
    });
  }

  filterLevel: number; // Ensures the depth doesn't exceed the maxFilterDepth (inception limit exceeded); Top level **MUST** start at 1
  id: number; // Used to sort filters according to creation date => id = Date.now() when created
  isGroupTF: boolean; // Determines whether the current filter is a rule or a rule set (AND/OR)
  clause: 'NA' | 'AND' | 'OR'; // (isGroupTF == true) Controls the AND/OR selector for the UI side ('NA' used for testing, should not be used in actual practice)
  dataField?: IDataField; // (!isGroupTF) This is the current filter's dataField value
  condition?: Condition; // (!isGroupTF) This is the current filter's condition value
  value: any; // (!isGroupTF) This is the current filter's value
  value2: any; // (!isGroupTF) This is the current filter's value2
  subFilters: Partial<Filter>[]; // (isGroupTF == true) The subFilters array contains all children to the current filter (rules or rule sets beneath the current rule set)
  boost: number; // Elastic specific property for boosting a specific filter's priority (1-10, defaulted at 5). Not required but added for future expansion
  slop: number; // Elastic specific property for allowing looser filtering based on the conditional property (0-10, defaulted at 1). Not required but added for future expansion
}

IDataField

interface IDataField {
  text: string; // The text that the users will see in the data field dropdown
  type: 'array' | 'string' | 'number' | 'date' | 'boolean' | 'json'; // Determines which conditions will show for this specific data field
  fieldName: string; // Column name reference field for the database
}

Condition

class Condition {
  text: string; // The text that the users will see in the conditional dropdown
  shortCode: string; // Short hand codes for referencing within the API/DB (rather than use "Less than or equal", you will see "lte", etc.)
  usedFor: string[]; // Determines what dataField types that can use this condition (don't need "Less than or equal" for a boolean type dataField)
  usesValue2?: boolean; // Tells the UI whether to display the 2nd value box or not, useful for using "Between" or "Not Between" comparators
  staticValue?: any; // If there is a static value that needs to be used, such as for the condition "empty/null" or "not empty/null", you don't actually need a value, but you need the value field to be filled with something (true/false/'')
}

IElasticFilter

export interface IElasticFilter {
  dataField?: string; // Filled with dataField value
  dataFields?: string[]; // TBD (used for testing)
  condition?: string; // Filled with condition value
  value?: string; // Filled with filter value
  value2?: string; // Filled with filter value2
  boost?: number; // Boost value
  slop?: number; // Slop value
  multiField?: string; // TBD (used for testing)
}

export interface IElasticFilterGroup extends IElasticFilter {
  // Used in place of IElasticFilter when isGroupTF == true
  filters: IElasticFilter[]; // child filters
  clause: ElasticFilterClause; // clause value ('AND'/'OR')
}

export enum ElasticFilterClause {
  NA = 0,
  AND = 1,
  OR = 2
}

Angular Conditionals

| ngx-qb | Angular | | -------- | --------- | | ^1.0.x | >= 13.x | | ^1.1.x | >= 20.x |

Non-included Dependencies

1. Bootstrap: Bootstrap is heavily relied upon for nearly the entire HTML portion, please ensure that the CSS file bootstrap.min.css from at least version 5 of bootstrap is included. This was intentionally not included in the package in order to make the package much smaller.
2. BrowserAnimationsModule: Must include at AppModule level for version 1.0.x. This should not be an issue for version 1.1.x.

Common Issues

1. Not including BrowserAnimationsModule in your module. Make sure that your AppModule, or containing module at least, has the BrowserAnimationsModule imported.
   • Note: this is specifically for using the built-in MatInput and MatButton elements. Your custom elements may or may not need this additional dependency.

License

MIT License - All parties who obtain a copy of the software and associated files are granted the right to use, copy, modify, merge, distribute, publish, sublicense, and sell copies of the software.

Acknowledgements

General Acknowledgements

My thanks go out to the owner(s) of the jQuery QueryBuilder for having their creation listed under an MIT License. Even though I have never actually dove into their code, the look, feel, and functionality of their examples all heavily inspired my own design choices for the NgxQB.

Individual Thanks

• Definitely thanks to Zach for inspiring me to build the component in the first place. He built the original consuming API and provided functional testing to ensure the component works as intended.

• Thanks also to Jay for inspiring me to actually pull out the component from the project that I had originally built it in and create a standalone importable library from it. As my first published NPM library, I definitely had to step out of my comfort zone to learn and do everything required for this but it was a great process to learn.

• Thanks to VIvek kale for requesting a patch to support Angular 19. Slighted revived this old project.