Forums Home / Wijmo / General Discussion
Posted by: stefan.brenner.a on 25 January 2024, 6:41 pm EST
stefan.brenner.a
Posted 25 January 2024, 6:41 pm EST
Hi,
I was trying to upgrade to Angular 17 and everything I define in ng-template no longer works. In another thread I read that Angular 17 is not yet supported. Is there an estimate when it will be supported and are there already any nightly builds with support?
Thanks and best regards,
Stefan
anirudh.verma
Posted 28 January 2024, 9:32 pm EST
Hi Stefan,
I am able to replicate the issue on my end and have informed about the same to the DEV team. Also, I have asked about the estimations for the Angular 17 support.
I will provide you with the updates as soon as I get any updates from the concerned team.
Please note the internal tracking id of the issue for further communication: WJM-33255
Thank you.
Regards
Anirudh
jgallais
Posted 29 January 2024, 8:10 pm EST
Hi,
Sorry, but i dont’ understand.
On your website (https://developer.mescius.com/wijmo/angular-ui-components) you say : “Our library was built-in TypeScript, requires zero dependencies, and supports Angular 17”
But here you say " Also, I have asked about the estimations for the Angular 17 support."
So is 5.20232.939 wijmo’s version support angular 17 or not ?
We made the migration to angular 17 last week, and this regression made our application unusabled 
Is it possible to give a clear guide line about this angular 17 support int this post please.
Thank’s a lot in advance.
Jonathan.
mark.brodziak
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.
anirudh.verma
Posted 1 February 2024, 12:37 am EST
Hi,
Sorry for the inconvenience caused.
There might be some misunderstanding. As mentioned in this link https://developer.mescius.com/wijmo/angular-ui-components , our Wijmo library is built-in TypeScript and our library has zero dependencies. Along with this, Wijmo supports Angular 17 that has typescript dependencies as mentioned in this page: https://angular.io/guide/versions. As mentioned in this blog: https://developer.mescius.com/blogs/wijmo-supports-angular-17, Wijmo can be used with Angular 17.0.0. However, it is not compatible with Server-Side Rendering in Angular.
We have tested Wijmo with 17.0.0 and it was working fine. You may also verify that the error related to the “ng-template (wjFlexGridCellTemplate) content not being displayed” was not occurring in Angular 17.0.0. Please refer to this sample for reference: https://stackblitz.com/edit/wj20232-flexgrid-wjflexgridcelltemplate-wdluqn
Therefore, there might be some issues in functionality of Wijmo with the later releases of Angular 17 because of implementation on either side. So, I have asked the DEV team to investigate it further for why the wjFlexGridCellTemplate is not working for later version of Angular.
Thank you for providing additional information. I have conveyed this information to the DEV team.
Also, I will mention the workaround(if any), as soon as I get any updates about the same from the DEV team.
Thank you for your understanding and patience.
Regards
jinder.sidhu
Posted 2 February 2024, 3:54 am EST
For us this has started happening since upgrading to Angular 17.1. When defining our own wj-flex-grid-column-group it looks like ColumnHeaders are being ignored (and potentially Cell templates too - need to investigate further). This is a problem only with 17.1.
Currently our migration to 17.1 is blocked due to this.
anirudh.verma
Posted 4 February 2024, 5:06 pm EST
Hi Jinder,
I am able to replicate the issue that the content used in wjFlexGridCellTemplate is not displayed in the respective cells while using ColumnGroups. I have informed the same to the DEV team. However, the ColumnGroups are working properly.
In case, if in your application, the ColumnGroups is not working properly then please share a sample replicating the issue.
Thank you.
Regards
mark.brodziak
Posted 5 February 2024, 5:08 pm EST
Hi Anridu, Jinder,
I have forked your StackBlitz and reproduced the problem that we are seeing:
https://stackblitz.com/edit/wj20232-flexgrid-wjflexgridcelltemplate-jcqcdk
The row headers were showing properly under earlier versions. Under this version we get console errors:
NG0303: Can't bind to 'cellType' since it isn't a known property of 'ng-template' (used in the 'App' component template).
1. If 'ng-template' is an Angular component and it has the 'cellType' input, then verify that it is included in the '@Component.imports' of this component.
2. If 'ng-template' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@Component.schemas' of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the '@Component.schemas' of this component.I can split it into another topic, if required.
anirudh.verma
Posted 6 February 2024, 2:59 pm EST
Hi Mark,
This issue is related to the original issue of using wjFlexGridCellTemplate directive. The DEV team is actively working on this issue. I will post the updates here as soon as I get any updates about the same from the DEV team.
For simpler use cases, you may use formatItem event, cellTemplate or CellMaker as per your use case. Please refer to the following links for more information:
cellTemplate: https://developer.mescius.com/wijmo/demos/Grid/CustomCells/CellTemplates/CommonTasks/purejs
formatItem: https://developer.mescius.com/wijmo/demos/Grid/CustomCells/ConditionalStyling/purejs
CellMaker: https://developer.mescius.com/wijmo/demos/Grid/CustomCells/CellMaker/Buttons/purejs
Thank you for your patience.
Regards
jinder.sidhu
Posted 11 February 2024, 9:22 pm EST
Any updates for when there will be a nightly fix for this?
anirudh.verma
Posted 12 February 2024, 3:41 pm EST
Hi,
We apologize for the inconvenience. The DEV team is currently exploring the issue. We’ll share updates as soon as we have them.
Thanks for your patience.
Regards
Anirudh
jinder.sidhu
Posted 22 February 2024, 9:12 pm EST
Any update in this? I hope this isn’t going to take months to deliver like your support for version 17. It’s very frustrating that Wijmo continues to be the library that causes us the most issues with upgrading.
anirudh.verma
Posted 22 February 2024, 11:09 pm EST
Hi Jinder,
We apologize for the inconvenience caused to you.
While the DEV team is still working on fixing this issue, they have suggested to use “cellTypeStr” instead of using “cellType” as the name of the property while using wjFlexGridCellTemplate.
Please refer to this code snippet for reference:
<ng-template wjFlexGridCellTemplate let-cell="cell" [cellTypeStr]="'Cell'">...</ng-template>Please refer to this sample for reference: https://stackblitz.com/edit/stackblitz-starters-v9vpwh
Regards
jinder.sidhu
Posted 26 February 2024, 2:08 am EST
This workaround has allowed us to upgrade - thanks.
anirudh.verma
Posted 26 February 2024, 4:27 pm EST
Hi Jinder,
Thank you for notifying me that the workaround was helpful to you. The DEV team is actively working on fixing this issue.
Thank you.
Regards
mark.brodziak
Posted 27 February 2024, 9:56 am EST
It works for us as well, thank you for the workaround.
weide.zhu
Posted 4 March 2024, 1:33 pm EST
we have the same issue here
vivek.pannu
Posted 4 March 2024, 4:47 pm EST
Hi Weide,
The dev team is working on this issue and it will be fixed soon. For now, please use the workaround we shared earlier, to avoid this issue. Here’s a copy of the response with the workaround -
"While the DEV team is still working on fixing this issue, they have suggested to use “cellTypeStr” instead of using “cellType” as the name of the property while using wjFlexGridCellTemplate.
Please refer to this code snippet for reference:
<ng-template wjFlexGridCellTemplate let-cell="cell" [cellTypeStr]="'Cell'">...</ng-template>Please refer to this sample for reference: https://stackblitz.com/edit/stackblitz-starters-v9vpwh "
Regards
corentin
Posted 20 March 2024, 7:24 pm EST
Hello,
With the new release of wijmo, this is no longer an issue.
We tried to update the version today and successfully removed the error.
Please mind the fact that you have to change every import statement from ‘@grapecity/’ to ‘@mescius/’.
Thanks to the developers team.
Corentin.
anirudh.verma
Posted 20 March 2024, 11:09 pm EST
Hi,
Thank you for your patience and understanding. This issue has been resolved in the latest release (https://www.npmjs.com/package/@mescius/wijmo/v/5.20241.7).
Please feel free to check it out.
Thank you.
Regards
