| Server IP : 78.140.185.180 / Your IP : 3.14.72.80 Web Server : LiteSpeed System : Linux cpanel13.v.fozzy.com 4.18.0-513.11.1.lve.el8.x86_64 #1 SMP Thu Jan 18 16:21:02 UTC 2024 x86_64 User : builderbox ( 1072) PHP Version : 7.3.33 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /home/builderbox/www/vendor/nyholm/psr7/doc/ |
Upload File : |
# Final classes The `final` keyword was removed in version 1.4.0. It was replaced by `@final` annotation. This was done due popular demand, not because it is a good technical reason to extend the classes. This document will show the correct way to work with PSR-7 classes. The "correct way" refers to best practices and good software design. I strongly believe that one should be aware of how a problem *should* be solved, however, it is not needed to always implement that solution. ## Extending classes You should never extend the classes, you should rather use composition or implement the interface yourself. Please refer to the [decorator pattern](https://refactoring.guru/design-patterns/decorator). ## Mocking classes The PSR-7 classes are all value objects and they can be used without mocking. If one really needs to create a special scenario, one can mock the interface instead.