Display a angular component in handsontable cell renderer

Tags: #<Tag:0x00007f0b0c24bd50> #<Tag:0x00007f0b0c24ba30>

I need to create a handsontable table that one of its columns is displayed in an Angular component, I have tried many things but it doesn’t work for me.

my angular component

import { Component } from ‘@angular/core’;


selector: ‘app-multi-select’,

template: `





  nzPlaceHolder="Please select"




    *ngFor="let item of listOfOption"





<ng-template #tagPlaceHolder let-selectedList

  >and {{ selectedList.length }} more selected</ng-template




export class MultiSelectComponent {

listOfOption = [‘Option 1’, ‘Option 2’, ‘Option 3’, ‘Option 4’, ‘Option 5’];

listOfSelectedValue: string[] = [];


similar to this example


but implement my own angular component

Hi @carlos

Thank you for contacting us. Unfortunately, currently it isn’t possible to declare a custom renderer as a component within Angular wrapper.

Ok. And manual renderer for transfor text in one cell type text

element 1, element 2

In this basic html


But when you select another cell you see the selected items separated with ‘,’

That is, the elements are stored separated by commas and when I select the cell, that small form opens to add or remove elements.


Hi @carlos

I’m sorry but I don’t quite understand your requirements. Do you want to build a custom editor with multiple choices in a dropdown?

i try this

but when I try to select a checkbox it closes, I imagine it has something to do with the editor, is there a way to select the checkboxes without it closing,

I show video for you to see.


I can only deselect/select by right clicking (the browser menu appears) and then I click on the checkbox, it is not visible in the gift, but I left a stackblizt link for them to corroborate

Hi @carlos

Thank you for the code and the explanation. I looked at your implementation and as it’s a custom logic it would require a code review from our side, so if you have an active license key send it to us at support@handsontable.com so we can check your current support plan.

I’d also recommend to check our example of custom editor (it’s in React, but the principles are the same) to check if the logic is correct as at the first view it seems that there is an issue with not preventing the editor to close before the chosen input item is selected.


sorry, actually no have license, i try develop a product, and when I see that I can translate my idea I would proceed to acquire a license.

Hi @carlos

I understand. Please, check the example I sent you and compare it with your implementation regarding the editor closing logic.