-
I have an SPA Angular/PrimeNG app that built and ran correctly, served up statically by Spring Boot, backed by a REST server and Keycloak for auth. It used Angular 12.2.3 and PrimeNG 12.1.1. I uninstalled my old Node.js, installed 20.13.1, installed Angular 17.3.0 and PrimeNG 17.16.1, created a new Angular workspace, and copied in the old project. Npm reported no errors with the installs. But ng build reports errors with p-table, as follows, code excerpt and error.
The
This produces `
` This worked before the upgrade. Angular somehow misses the membership of poNumber in the ReleaseData, thinks it should be in the component. Thanks for any comments. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The solution is
and
This at least suppresses the build error, presumably it will also run. The PrimeNG p-tablel doc needs to be corrected. |
Beta Was this translation helpful? Give feedback.
The solution is
<p-table value="releases" let-column...>
and
<th
[pSortableColumn]="column.poNumber" pResizableColumn>PO Number<p-sortIcon [field]="column.poNumber">This at least suppresses the build error, presumably it will also run. The PrimeNG p-tablel doc needs to be corrected.