Stamen Stoychev

Hello @armeireles , Yes, it's still Oct 5. For the first release of the component we are only exposing a getter/setter that's basically a representation of the QB model and...

@armeireles , you should be able to use the Query Builder with 14.2.0-alpha.4 . Docs/samples are still being worked on but you can get a decent idea on how to...

Hello @armeireles , you have probably seen already, but 14.2.0 has been released and you can access the QueryBuilder documentation following this link: https://www.infragistics.com/products/ignite-ui-angular/angular/components/query-builder For the first release we exposed...

@ntziolis , sorry forgot to change the label! It's been in development since last week but it requires some refactoring so it might take a few more days. Hopefully, we...

@mikerentmeister , if you don't need the typescript path and can just import from '@infragistics\igniteui-angular' I think we can solve this. In that case the only problem I found was...

Yes, this is what I mentioned we can fix easily. Try removing the tripple slash (///) comment from node_modules/@infragistics/igniteui-angular/index.d.ts

I think I also needed to do `npx jest --clearCache` Anyhow, I'll prepare the project to share to you but I'll need some time to go back step by step...

Glad it worked. Step 3 should be omittable from the next patch (14.0.10 expected on Monday) onward. Please, let me know when you are able to give it a try....

This is a side effect of how ngIf handles destroying the content under the hood. It actually tries to be smart about it to be able to recreate it more...

We'll be assigning it for further investigation most likely very early in November, after the current cycle of development is complete. Generally speaking, Angular makes memory leak hunting a lot...