Skip to content

Replies

0
Martin Pavlov
Martin Pavlov answered on Jul 3, 2019 7:27 AM

Hello Suprasanna,

 

Let me know if you still need assistance regarding this issue.

 

Best regards,

Martin Pavlov

Infragistics, Inc.

0
Martin Pavlov
Martin Pavlov answered on Jun 17, 2019 11:27 AM

Hello Suprasanna,

I believe the same issue is discussed here: https://github.com/IgniteUI/igniteui-angular/issues/5077. You can subscribe to the issue in GitHub to get notifications.

Best regards,
Martin Pavlov
Infragistics, Inc.

0
Martin Pavlov
Martin Pavlov answered on Jan 30, 2018 9:39 AM

Hello Bharati P,

Not sure. We didn't test a mix of component versions and doesn't support it. Is there a specific reason that requires such configuration?

Best regards,
Martin Pavlov
Infragistics, Inc.

0
Martin Pavlov
Martin Pavlov answered on Jan 30, 2018 7:44 AM

Hello Bharathi P,

 

We don't have a way to get the product version other than the one that I suggested you. Each control has its own version. If the controls are from the same build, all of them will return one and the same product version.

 

Best regards,

Martin Pavlov
Infragistics, Inc.

0
Martin Pavlov
Martin Pavlov answered on Jan 29, 2018 7:09 AM

Hello Bharathi P,

Yes. In the browser JavaScript console write:

$.ui.<widget_name>.version

For example if you have an igGrid on the page then write:

$.ui.igGrid.version

For igUpload is:

$.ui.igUpload.version

 

Best regards,

Martin Pavlov
Infragistics, Inc.

0
Martin Pavlov
Martin Pavlov answered on Jul 25, 2017 1:51 PM

Hello Espen,

There is a new release 4.0.3 of the Ignite UI Angular 2 directives which fixes GitHub issue #178.

Best regards,
Martin Pavlov
Infragistics, Inc.

0
Martin Pavlov
Martin Pavlov answered on Jul 25, 2017 8:59 AM

Hello Espen,

This is an issue in the wrappers. I logged it on GitHub: https://github.com/IgniteUI/igniteui-angular2/issues/178
You can subscribe to the issue to get notifications for it.

Best regards,
Martin Pavlov
Infragistics, Inc.