Unashughulikia vipi exceptions ipasavyo?

Question

Accepted Answer

PHP hushughulikia errors kwa **exceptions** zinazonaswa kupitia `try/catch/finally`. Exception handling ipasavyo humaanisha kunasa types mahususi, kuunda meaningful custom exceptions, kusafisha resources, na kamwe kutowafichua users maelezo ya ndani. ## Muundo wa msingi ```php getMessage()); } catch (DatabaseException $e) { handleDbError($e); } catch (Throwable $e) { // catch-all (Error OR Exception) — last logError($e); throw $e; // re-throw what you can't handle } finally { cleanup(); // ALWAYS runs (success or failure) } ``` Nasa exception types **mahususi** (mahususi zaidi kwanza), tumia `Throwable` kama catch-all ya mwisho (inashughulikia `Error` na `Exception` zote), na tumia `finally` kwa cleanup ambayo lazima iendeshwe daima. ## Kuzua na custom exceptions ```php // throwing if ($amount < 0) { throw new InvalidArgumentException("Amount must be positive, got $amount"); } // a custom exception for your domain class InsufficientFundsException extends Exception { public function __construct(private float $shortfall) { parent::__construct("Short by $shortfall"); } public function getShortfall(): float { return $this->shortfall; } } throw new InsufficientFundsException(50.0); ``` Custom exception classes huzifanya error handling kuwa za kueleweka na huwawezesha callers kunasa domain errors mahususi. ## Exception chaining (hifadhi chanzo) ```php try { $db->query(...); } catch (PDOException $e) { // wrap with context, preserving the original as the "previous" exception throw new RepositoryException("Failed to load user", 0, $e); } ``` Argument ya tatu ya constructor hu-chain exception ya awali (`$e->getPrevious()`), ikihifadhi chanzo kamili kwa debugging. ## Mazoea bora ```text ✓ Catch SPECIFIC exceptions, not a blanket Throwable (unless intentionally last) ✓ Don't swallow exceptions silently (empty catch) — log or re-throw ✓ Use finally / proper cleanup for resources (files, connections) ✓ Create meaningful custom exceptions for domain errors ✓ SECURITY: log details internally; show users a generic message (don't leak stack traces / internal info — display_errors off in production) ``` ## Kwa nini ni muhimu Exception handling ipasavyo ni muhimu kwa kujenga PHP applications imara, za kuaminika, na salama. Kuelewa muundo wa `try/catch/finally`, kunasa exception types **mahususi** (kwa handling iliyolengwa) na `Throwable` kama catch-all ya mwisho (inashughulikia `Error` na `Exception` zote katika PHP ya kisasa), na kutumia `finally` kwa cleanup iliyohakikishwa ni ujuzi wa kila siku wa msingi. Zaidi ya mechanics, mazoea bora yana umuhimu: kuunda **meaningful custom exceptions** kwa domain errors huzifanya code kuwa za kueleweka na huwawezesha callers kushughulikia failures mahususi; **exception chaining** huhifadhi chanzo cha msingi kwa debugging; na muhimu, **kutomeza exceptions kimyakimya** (kuandika logs au kuzua tena badala yake) huzuia failures zilizofichwa. Jambo muhimu hasa ni **usalama**: exceptions na errors zinapaswa **kuandikwa logs ndani lakini kamwe kufichuliwa kwa users** (stack traces na maelezo ya ndani hufichua taarifa nyeti na husaidia washambuliaji — ndiyo maana `display_errors` huzimwa katika production). Kujua jinsi ya kushughulikia exceptions ipasavyo — specific catches, custom exceptions, cleanup, chaining, na secure logging badala ya kufichua — hutofautisha PHP imara, ya kitaalamu na code dhaifu inayoanguka bila utaratibu au kufichua taarifa, na hivyo kuifanya ujuzi muhimu kwa kujenga applications za kuaminika na salama.