Vue Data GridGrid Interface

This section details the public interface that your application can use to interact with the grid, including methods, properties and events.

The grid interface is the combination of the following items:

  • Grid Options: properties and callbacks used to configure the grid, e.g. pagination = true and getRowHeight(params).
  • Grid API: methods used to interact with the grid after it's created, e.g. api.getSelectedRows().
  • Grid Events: events published by the grid to inform applications of changes in state, e.g. rowSelected.
  • Row Node: each row in the grid is represented by a Row Node object, which in turn has a reference to the piece of row data provided by the application. The Row Node wraps the row data item. The Row Node has attributes, methods and events for interacting with the specific row e.g. rowNode.setSelected(true).

Properties, Events, Callbacks and APIs

  • Attributes: attributes are properties, but aren't bound - they are instead provided literal values (e.g. rowSelection="multiple").
  • Properties: properties are bound attributes (e.g. :columnDefs="columnDefs").
  • Callbacks: callbacks are bound in the same as properties are (e.g. :getRowHeight="myGetRowHeightFunction").
  • Event Handlers: event handlers are are bound in the standard way (e.g. @cell-clicked="onCellClicked"). Event names must use kebab-case.
  • API: the grid API and column API are accessible through the component.

All of the above (attributes, properties, callbacks and event handlers) are registered using their 'dash' syntax and not camel-case. For example, the property pivotMode is bound using pivot-mode. The following example shows some bindings:

    // these are attributes, not bound, give explicit values here

    // these are boolean values
    // (leaving them out will default them to false)

    // these are bound properties

    // this is a callback

    // these are registering event callbacks

Access the Grid & Column API

When the grid is initialised, it will fire the gridReady event. If you want to use the APIs of the grid, you should put an onGridReady(params) callback onto the grid and grab the api(s) from the params. You can then call these apis at a later stage to interact with the grid (on top of the interaction that can be done by setting and changing the properties).

     // provide gridReady callback to the grid
     // ...

 // in onGridReady, store the api for later use
 onGridReady = (params) => {
     this.api = params.api;
     this.columnApi = params.columnApi;

The APIs are then accessible through the component:

<button @click="this.api.deselectAll()">Clear Selection</button>

Grid Options

The gridOptions object is a 'one stop shop' for the entire interface into the grid, commonly used if using plain JavaScript. Grid options can however be used instead of, or in addition to, normal framework binding. If an option is set via gridOptions, as well as directly on the component, then the component value will take precedence.

The example below shows the different types of items available on gridOptions.

const gridOptions = {
     // Objects like myRowData and myColDefs would be created in your application
     rowData: myRowData,
     columnDefs: myColDefs,
     pagination: true,
     rowSelection: 'single',

     // EVENTS
     // Add event handlers
     onRowClicked: event => console.log('A row was clicked')
     onColumnResized: event => console.log('A column was resized')
     onGridReady: event => console.log('The grid is now ready')

     getRowHeight: (params) => 25

Once the grid is initialised, you will also have access to the grid API (api) and column API (columnApi) on the gridOptions object as shown:

// refresh the grid

 // resize columns in the grid to fit the available space

Events Are Asynchronous

Grid events are asynchronous so that the state of the grid will be settled by the time your event callback gets invoked.

Default Boolean Properties

Where the property is a boolean (true or false), then false (or left blank) is the default value. For this reason, on / off items are presented in a way that causes the most common behaviour to be used when the value is false. For example, suppressCellFocus is named as such because most people will want cell focus to be enabled.

Next Steps

That's it, Doc! Now you know how to interface with the grid. Go now and find out about all the great options, methods and events you can use.