Posted 30 January 2024, 10:12 am EST
I think we just hit the same issue when attempting to do a patch update of Angular.
Interestingly, our application seemed to be working just fine under Angular 17.0.5 (we upgraded late last year), but we only started encountering errors under Angular 17.0.7+ (and, specifically the issue pops up in 17.0.7)
In our case, the symptom shows up as:
NG0303: Can't bind to 'cellType' since it isn't a known property of 'ng-template'
I am guessing that this might be the change that is impacting Wijmo, but it is hard to know for sure: https://github.com/angular/angular/pull/51474
We’d really appreciate a prompt resolution and/or workaround so that we can move forward.
Honestly, it seems that moving forward it might be prudent to minimize use of Wijmo’s Angular layer and deal with that ourselves by using the lower level Wijmo API (basically, drop our use of templated Wijmo grids and configure the grid in TypeScript). We’re already doing this for our more complex grid integrations and these are not impacted by the above problem.
We’re not comfortable with the situation that core framework updates are held back by a library. Worse is when (apparently) a patch release of Angular breaks the application because of this library.
Hopefully the above information gives a clue to the dev team so that they can identify and address the issue.