Damyan Petev
Damyan Petev
@kdinev Well I have to look at the small utils things that weren't tree shaking after the updates anyway, so I might as well have a look at the highlight...
I realize this can be easily worked around for this scenario and possibly in a few other cases. Still, quite odd to have to explain `columnInit` args can be used...
Like I said, that would only help if we didn't have the problematic props on those as well (we do), so both changes will likely be breaking one way or...
Likely the same issue that's affecting the Select in the paging when switching to Bootstrap? https://staging.infragistics.com/products/ignite-ui-angular/angular/components/grid/paging
Right, since 15.1.x is still in active support that means Angular 15 which still supports Node.js 14 https://angular.io/guide/versions#actively-supported-versions, which in turn is the last version that bundled npm 6 https://nodejs.org/en/download/releases....
@AnjiManova Is it me or the [Design Handoff in the spec](https://github.com/IgniteUI/igniteui-webcomponents/wiki/Date-picker-specification#end-user-experience) only deals with the actual calendar popup but nothing on the input or component as a whole. I realize...
> > [...] > > @damyanpetev, no, it's not you; in the handoff, the main focus was on the popup, and yes, you are right - the date picker compound...
The branch is quite a bit behind and syncing in full can have some unforeseen effects and require more revalidation - still agree it needs to be done as soon...
Done. Next internal build should have this fix in