{
  "id": 10260274,
  "title": "Laravel Context: The Hidden Information That Follows Your Code",
  "url": "https://urgent.news/2026/09/27/laravel-context-the-hidden-information-that-follows-your-code",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-27T17:33:15.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/othmane_nemli/laravel-context-the-hidden-information-that-follows-your-code-1mo8"
  },
  "original_language": "en",
  "account": null,
  "summary": "When working with Laravel, we usually pass data explicitly: $user = auth () -> user (); UserExampleService :: process ( $user ); Or we add information directly to a log: Log :: info ( 'Processing order' , [ 'order_id' => $order -> id , ]); But what if you have some information that should be available throughout the current execution? For example: a trace ID the current URL a tenant ID an…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}