Missing Documentation for Breaking Changes in PrimeNG 19

[vrjaroslav]

Hi,

Thank you for the new version; it looks great. However, I found several undocumented changes—or perhaps they are documented, but I couldn’t find the relevant information. For example, in the Table component, in version 17, I used the following code:

<p-table styleClass="p-datatable-sm p-datatable-gridlines p-datatable-striped">

Where:

• p-datatable-sm was for the small size of the table.
• p-datatable-gridlines was for grid lines.
• p-datatable-striped was for striped rows.

None of these work in the new version. After reviewing the documentation for PrimeNG 19, I discovered that:

• size="small" should now be used instead of p-datatable-sm.
• showGridlines should replace p-datatable-gridlines.
• stripedRows should replace p-datatable-striped.

Next things what I found:

Checkbox Issue
In version 17, the following code worked:

<p-checkbox label="Cheese" />

However, in version 19, this no longer works and must be replaced with:

<p-checkbox></p-checkbox>  
<label>Cheese</label>

Radio Button Issue
In version 17, the following code worked:

<p-radiobutton label="Cheese" />

However, in version 19, this no longer works and must be replaced with:

<p-radiobutton></p-radiobutton>  
<label>Cheese</label>

I couldn’t find any mention of these breaking changes in the migration guide: [PrimeNG Migration Guide](https://primeng.org/guides/migration). These changes are significant and breaking, yet they seem undocumented.

If these changes are documented, it would make updating the code much easier. Unfortunately, I now have to manually identify what doesn’t work across all projects and spend time comparing the documentation for versions 17 and 19 to figure out the differences.

Could you please provide a link or point me to where these significant breaking changes are documented?

[vrjaroslav]

Next thing, in v17,

import { InputTextareaModule } from 'primeng/inputtextarea';

<textarea rows="5" cols="30" pInputTextarea  [(ngModel)]="value">
</textarea>

in v19

import { TextareaModule } from 'primeng/textarea';

<textarea rows="5" cols="30" pTextarea [(ngModel)]="value"></textarea>

Again, there is nothing in the migration guide about it. Is this the right place to post my question? Nobody has replied yet. I am disappointed, as these are really big breaking changes, and I have to spend a lot of time finding all the issues.

[vrjaroslav]

Next thing:

severity warning was changed to warm

v17
<p-tag severity="warning" value="Warning"/>

v19
<p-tag severity="warn" value="Warning"/>

[vrjaroslav]

Next thing:

Element p-confirmDialog was changed to p-confirmdialog

v17:

<p-confirmDialog />

v19:
<p-confirmdialog />

[djay1977]

Only in CSS, not in tag

[davidda]

<span class="p-float-label">...</span>

needs to be replaced by

<p-floatlabel>...</p-floatlabel>
importing FloatLabelModule

[davidda]

<p-dialog><p-header></p-header><p-footer></p-footer></p-dialog>

needs to be replaced by

<p-dialog><ng-template #header>...</ng-template><ng-template #footer>...</ng-template></p-dialog>

[davidda]

Input Groups need to be changed from class-based class="p-inputgroup" to element-based <p-inputgroup>

[davidda]

Although the renames of components such as
Dropdown -> Select
are supposed to be backwards compatible, they are actually breaking changes. The reason is that some things just stop working with the "old" names. Example: #17331 (which also applies to calendar and possibly others)

[TheAfterman]

I will add my findings in addition to the ones already mentioned above (most of which also tripped me up). Must say I'm disappointed by the number of breaking/undocumented changes and secretly removed functionality in v18/19. I appreciate your hard work though.

• showCloseIcon is still documented at https://primeng.org/popover but the functionality has been removed
• arrow positioning on p-popover no longer works correctly. You can see this if you make the window small on any of the https://primeng.org/popover demos. Do the same on https://v17.primeng.org/overlaypanel to see how it should work.
• the p-tabPanel [header] attribute must now be replaced by a separate <p-tablist></p-tablist> to define the text in each tab. This is worse imo because now you have to loop twice for dynamic tab lists - once for the tabs and separately for the tabs content under <p-tablist>. Regardless, this should surely be mentioned in migration guide as it's a significant breaking change.
• p-tabs (onChange) and (onClose) outputs have been removed
• [closable] attribute on v17 p-tabPanel has no equivalent functionality in v18/19. We must now manually implement our own tab close template/functionality.

[davidda]

Generally, template works a little differently. Like
<ng-template pTemplate="item">
needs to be replaced by
<ng-template #item>

(the old syntax still works in many but not all cases)