Book Image

The Art of Modern PHP 8

By : Joseph Edmonds
5 (1)
Book Image

The Art of Modern PHP 8

5 (1)
By: Joseph Edmonds

Overview of this book

PHP has come a long way since its introduction. While the language has evolved with PHP 8, there are still a lot of websites running on a version of PHP that is no longer supported. If you are a PHP developer working with legacy PHP systems and want to discover the tenants of modern PHP, this is the book for you. The Art of Modern PHP 8 walks you through the latest PHP features and language concepts. The book helps you upgrade your knowledge of PHP programming and practices. Starting with object-oriented programming (OOP) in PHP and related language features, you'll work through modern programming techniques such as inheritance, understand how it contrasts with composition, and finally look at more advanced language features. You'll learn about the MVC pattern by developing your own MVC system and advance to understanding what a DI container does by building a toy DI container. The book gives you an overview of Composer and how to use it to create reusable PHP packages. You’ll also find techniques for deploying these packages to package libraries for other developers to explore. By the end of this PHP book, you'll have equipped yourself with modern server-side programming techniques using the latest versions of PHP.
Table of Contents (19 chapters)
Section 1 – PHP 8 OOP
Free Chapter
Chapter 1: Object-Oriented PHP
Section 2 – PHP Types
Chapter 5: Object Types, Interfaces, and Unions
Section 3 – Clean PHP 8 Patterns and Style
Section 4 – PHP 8 Composer Package Management (and PHP 8.1)
Section 5 – Bonus Section - PHP 8.1

Using versions and tagging

It is fully expected that your package will not be perfect the moment you publish. Even if you did somehow manage to achieve perfection, the world keeps changing, and you might find that the latest PHP version that has just come out requires some tweaks to your code. You need to provide a mechanism for projects that are using your package to make sure they only get the known, safe versions that they want.

When you update your library and hit a stable point that you would like to release as a new version that is ready to be used in production projects, all you need to do is create a Git tag with a semantic version (to be explained soon) and push this up to the VCS that Packagist is connected to – for example, GitHub:

Resources to learn Git

Creating a Git tag

Before you can create a tag, you must have created at least one commit. In general, there will be a whole sequence of commits leading up to the point where...