Skip to content

error-handling.md

Latest commit

 

History

History
62 lines (42 loc) · 1.71 KB

error-handling.md

File metadata and controls

62 lines (42 loc) · 1.71 KB

Error Handling

All package-specific failures extend SessionException.

Related pages:

Exception Types

  • SessionException: base exception for the package.
  • SessionDriverException: wraps unexpected driver failures.
  • InvalidSessionDriverException: invalid driver classes, creation failures, or driver switching after start.
  • SessionNotStartedException: data or lifecycle operation requires an active session.
  • SessionStartException: driver could not start a session.
  • SessionStorageException: storage operation failed after start.
  • CorruptSessionDataException: a named session namespace is not array data.

Expected Usage Errors

Reading before start throws:

$session = new SessionManager($driver);

$session->get('user_id'); // SessionNotStartedException

Switching drivers after start throws:

$session->start();
$session->useDriver($otherDriver); // InvalidSessionDriverException

Using a named bag over scalar data throws:

$session->set('profile', 'not an array');
$session->bag('profile'); // CorruptSessionDataException

Driver Failures

Drivers should throw session exceptions directly when they can explain the failure.

Unexpected throwables are wrapped by SessionManager:

try {
    $session->start();
} catch (SessionDriverException $exception) {
    $previous = $exception->getPrevious();
}

Native Driver Failures

The native driver captures warnings from session_start(), session_write_close(), session_regenerate_id(), session_destroy(), session_name(), and session_id().

Captured warnings become package exceptions so callers do not need to install their own temporary PHP error handlers.