Boris Penkov

There seem to be some problems with the edited components/views: 1. The radio group doesn't show at all. 2. The dropdown throws when you try to expand it. 3. The...

Hi @gazoonie, this behavior is by design as we want to have the single selection combo's interactions be as similar as possible to the multi selection combo's and in the...

Since the outlined problem here comes from the CG - the problem is not with the input directive but with the generation. The current generation outputs this for NGM: ...

After a little bit of research, I think we may need to redesign the way the `time picker` handles scrolling. Right now we listen for `scroll` or `pan` events and...

@lalo-mx in our case the usage of the native `` is not plausible since there are differences in the component's UI and behavior depending on the platform/browser. Our goal is...

@Lipata Even though the CLI will not be used to generate routing, etc, it is still a good idea to get rid of `lerna/yarn` and just use `npm` workspaces. So...

Tested with [18.1.0-alpha.1](https://www.npmjs.com/package/igniteui-angular/v/18.1.0-alpha.1) and everything seems to be alright.

The changes look good, though I have a little question. With the introduction of the `editorOptions` property on the column, I can now set the `dateTimeFormat` of the column which...

> > With the introduction of the `editorOptions` property on the column, I can now set the `dateTimeFormat` of the column which properly applies the mask/date string I've set while...

The reason why this error occurs is because currently the upgrade logic relies on the existence of an `ignite-ui-cli.json`. Let me try to shed some light on what's happening. First,...