Just a side note for new developers: when Jeremy fills out an array of characters as ticket statuses in the TicketFactory class — in cases like this, consider using enums that were introduced back in PHP 8.1.

You will do yourself a favor in the long run since you will not need to refer to some external documentation or remembering what each character or number meant. With enums, you can replace "A" and other status symbols or numbers with enum cases in your code like TicketStatus::ACTIVE instead of just "A", etc., while the enum case will still be "backed" by a string like "A" or an integer, so you will keep these values as small as possible in your database, but in your code you will have a perfectly readable native syntax of PHP enums, with auto-complete, too.

That way, you'll always have these self-documenting objects in your code base that you can always refer to, and they will stay consistent throughout your project due to originating from a single source of truth. Before enums, you could've always achieved similar results with constants, but enums just make it way clearer and more consistent.

Incorporate enums in your code as soon as possible and make it a "healthy" habit to use them, you'll love it and will thank yourself later down the road!

Designing the Url