Maya

@mddragnev @dkamburov @hanastasov I have added a new event for the igxGridState directive that can be used to modify the state before applying it when it is passed as a...

@mddragnev Issue should be fixed now.

I’ve been thinking about it, and since the customer that wants this feature does not wants to have any configuration options (uses a predefined configuration and just want to display...

@dkamburov Note that this changes the structure in the Grid as well, so this PR should be tested for WC, React, Blazor for Grid, TreeGrid, HierarchicalGrid and PivotGrid.

@wnvko @dkamburov I'm not that familiar with the combo, but looking at the docs: https://www.infragistics.com/products/ignite-ui-angular/angular/components/combo#two-way-binding It seems that the bindings expect just an array of the simple value associated with...

@damyanpetev @mddragnev @dkamburov When debugging it, indeed it seem that the issue is that the columnInit emits the original angular column object, which expects a TemplateRef for the bodyTemplate. So...

@damyanpetev The typings for the columns are hardcoded in the api analyzer right now. They are the original angular's ColumnyType but are explicitly mapped to IgcColumn instead: https://github.com/IgniteUI/igniteui-api-analyzer/blob/master/src/MetadataManager.ts#L562 Perhaps we...

I believe it was logged because the workaround for restoring column templates as described in the angular docs: https://www.infragistics.com/products/ignite-ui-angular/angular/components/grid/state-persistence#restoring-columns Doesn't work the same way for wc. But it can be...

@dkamburov After investigating this some more it seems that this will work on initial load, but if the columns get re-created internally for some reason- for example if the state...

@mddragnev IMO it might be tricky to match the columns from the state's string to the actual columns, since the columns don't really have an unique identified. They have `field`...