Semantic Versioning Issues

[jarekcimoch]

Hi, we are using prime-ng as our main UI library for over 2 years now and we encounter breaking changes issues each minor releases updates. I don't want to list all of them here, I think any user of this library is aware that changelog can't be fully trusted and we face breaking changes in components or services on multiple layers, from method renames to new required parameters, ending on totally new structure in htmls. When we combine the fact that a lot of teams is overriding some stylesheets to their needs and structural changes are introduced behind the scenes we can't properly estimate the effort of migration.

Could you maybe do something about it and improve the process of communication and changelog? I think Angular repository is good open source example how changelog, migration guidelines and docs should look like. It's really pain in the neck to work on enterprise level application with such poor migration processes.

[DaSchTour]

I have a bit the impression that the 18/19 release was a bit rushed. What bothers me the most is that there are no unit tests for the components which could ensure a minimum of stability. As we just recently started using PrimeNG components it's currently not such a pain. But we already had discussions with which issues of PrimeNG components we can live for some time.
But actually I didn't find any real good alternative to PrimeNG especially with the amount of also complex components. But it somehow feels like it would be better to write components yourself. I would also like to help with the components, but with no testing infrastructure in place it's pretty hard. Also there is very little feedback on the PRs I made. So I have no idea if and when the fixes I propose might be available.