Slickgrid-Universal ships with a few default inline editors (checkbox, dateEditor, float, integer, text, longText).
Note: For the Float Editor, you can provide decimal places with params: { decimals: 2 } to your column definition else it will be 0 decimal places by default.
Required Grid Option
Editors won't work without these 2 flags enableCellNavigation: true and editable: true enabled in your Grid Options, so make sure to always to always defined them. Also note that you can toggle the grid to read only (not editable) via the editable grid option flag.
How to use Inline Editors
Simply call the editor in your column definition with the Editors you want, as for example (editor: { model: Editors.text }). Here is an example with a full column definition:
For SalesForce the code is nearly the same, the only difference is to add the Slicker prefix, so instead of Editors.abc we need to use Slicker.Editors.abc, ...
Demo with Float Editor and Dollar Currency Formatter
This probably comes often, so here's all the setting you would need for displaying & editing a dollar currency value with 2 decimal places.
this.columnDefinitions = [
{
id: 'cost', name: 'Cost', field: 'cost',
type: 'float',
formatter: Formatters.dollar, // the Dollar Formatter will default to 2 decimals unless you provide a minDecimal/maxDecimal
// params: { minDecimal: 2, maxDecimal: 4, }, // optionally provide different decimal places
// the float editor has its own settings, `decimal` that will be used only in the editor
// note: that it has nothing to do with the Dollar Formatter
editor: { model: Editors.float, decimal: 2 },
},
];
Editor Output Type & Save Output Type
You could also define an outputType and a saveOutputType to an inline editor. There is only 1 built-in Editor with this functionality for now which is the dateEditor. For example, on a date field, we can call this outputType: 'dateIso' (by default it uses dateUtc as the output):
this.columnDefinitions = [
{
id: 'start', name: 'Start', field: 'start',
type: 'date',
editor: { model: Editors.date },
type: 'date', // dataset cell input format
// outputType: 'dateUs', // date picker format
saveOutputType: 'dateUtc', // save output date format
}
];
So to make it more clear, the saveOutputType is the format that will be sent to the onCellChange event, then the outputType is how the date will show up in the date picker (Vanilla-Calendar) and finally the type is basically the input format (coming from your dataset). Note however that each property are cascading, if 1 property is missing it will go to the next one until 1 is found... for example, on the onCellChange if you aren't defining saveOutputType, it will try to use outputType, if again none is provided it will try to use type and finally if none is provided it will use 'dateIso' as the default.
Perform an action After Inline Edit
Recommended way
Not recommended
You could also, perform an action after the item changed event with onCellChange. However, this is not the recommended way, since it would require to add a onCellChange on every every single column definition.
Custom Inline Editor
Once you are done with the class, just reference it's class name as the editor, for example:
How to prevent Editor from going to the next bottom cell?
The default behavior or SlickGrid is to go to the next cell at the bottom of the current cell that you are editing. You can change and remove this behavior by enabling autoCommitEdit which will save current editor and remain in the same cell
Some of the Editors could receive extra options, which is mostly the case for Editors using external dependencies (e.g. autocompleter, date, multipleSelect, ...) you can provide options via the editor options, for example
this.columnDefinitions = [{
id: 'start', name: 'Start Date', field: 'start',
editor: {
model: Editors.date,
// previously known as `editorOptions` for < 9.0
options: { displayDateMin: 'today' } as VanillaCalendarOption
}
}];
Grid Option `defaultEditorOptions
You could also define certain options as a global level (for the entire grid or even all grids) by taking advantage of the defaultEditorOptions Grid Option. Note that they are set via the editor type as a key name (autocompleter, date, ...) and then the content is the same as editor options (also note that each key is already typed with the correct editor option interface), for example
Each Editor needs to implement the validate() method which will be executed and validated before calling the save() method. Most Editor will simply validate that the value passed is correctly formed. The Float Editor is one of the more complex one and will first check if the number is a valid float then also check if minValue or maxValue was passed and if so validate against them. If any errors is found it will return an object of type EditorValidatorOutput (see the signature on top).
Custom Validator
If you want more complex validation then you can implement your own Custom Validator as long as it implements the following signature.
export type EditorValidator = (value: any, args?: EditorArgs) => EditorValidatorOutput;
So the value can be anything but the args is interesting since it provides multiple properties that you can hook into, which are the following
So if we take all of these informations and we want to create our own Custom Editor to validate a Title field, we could create something like this:
const myCustomTitleValidator: EditorValidator = (value: any, args: EditorArgs) => {
// you can get the Editor Args which can be helpful, e.g. we can get the Translate Service from it
const grid = args?.grid;
const gridOptions = (grid && grid.getOptions) ? grid.getOptions() : {};
const i18n = gridOptions.i18n;
if (value == null || value === undefined || !value.length) {
return { valid: false, msg: 'This is a required field' };
} else if (!/^Task\s\d+$/.test(value)) {
return { valid: false, msg: 'Your title is invalid, it must start with "Task" followed by a number' };
// OR use the Translate Service with your custom message
// return { valid: false, msg: i18n.tr('YOUR_ERROR', { x: value }) };
} else {
return { valid: true, msg: '' };
}
};
If your grid uses the autoResize and you use Editors in your grid on a mobile phone, Android for example, you might have undesired behaviors. It might call a grid resize (and lose input focus) since the touch keyboard appears. This in term, is a bad user experience to your user, but there is a way to avoid this, you could use the pauseResizer
View
<div id="grid1">
</div>
Component
attached() {
const dataset = this.initializeGrid();
const gridContainerElm = document.querySelector<HTMLDivElement>(`.grid4`);
gridContainerElm.addEventListener('onslickergridcreated', this.handleOnSlickerGridCreated.bind(this));
this.slickgridLwc = new Slicker.GridBundle(gridContainerElm, this.columnDefinitions, this.gridOptions, dataset);
}
handleOnSlickerGridCreated(event) {
this.slickerGridInstance = event && event.detail;
this.gridObj = this.slickerGridInstance && this.slickerGridInstance.slickGrid;
this.dataViewObj = this.slickerGridInstance && this.slickerGridInstance.dataView;
}
onAfterEditCell($event) {
// resume autoResize feature, and after leaving cell editing mode
// force a resize to make sure the grid fits the current dimensions
this.slickerGridInstance.resizerService.pauseResizer(false);
this.slickerGridInstance.resizerService.resizeGrid();
}
onBeforeEditCell($event) {
this.slickerGridInstance.resizerService.pauseResizer(true);
}
SalesForce (ES6)
For SalesForce it's nearly the same, the only difference is that we add our events in the View instead of in the ViewModel
You can dynamically change a column editor by taking advantage of the onBeforeEditCell event and change the editor just before the cell editor opens. However please note that the library keeps 2 references and you need to update both references as shown below.
With the code sample shown below, we are using an input checkbox to toggle the Editor between Editors.longText to Editors.text and vice/versa
What is ideal is to bind to a SlickGrid Event, for that you can take a look at this
To create a Custom Editor, you need to create a class that will extend the and then use it in your grid with editor: { model: myCustomEditor } and that should be it.
Instead of an inline editor, you might want to simply click on an edit icon that could call a modal window, or a redirect URL, or whatever you wish to do. For that you can use the inline onCellClick event and define a callback function for the action (you could also create your own ).
This can be answered by searching on Stack Overflow Stack Overflow and this is the best found.
Using the you can let the user toggle either one or multiple rows into edit mode, keep track of cell changes and either discard or save them on an individual basis using a custom onBeforeRowUpdated hook.