DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to save typed decisions in an Eloquent JSON column with Laya PHP

Cast a model attribute to a decision class so the result reads back as a typed object.

Who it is forA Laravel developer who wants to keep each classification result on the record it describes, without writing parsing code.

The problemStoring classification output as loose arrays loses the enum and type information, and every read needs manual conversion.

The outcomeThe model attribute holds a typed decision, and it reads back with enums and floats intact.

What you need first

  • PHP 8.4+ and Composer
  • A PSR-18 HTTP client such as Guzzle or Symfony HttpClient
  • Docker, to run laya-serve from the repo's compose.yaml
  • Laravel 13+ for the Laravel steps (service provider, artisan commands, validation rule, cast)

Steps

  1. Run composer require marcreichel/laya-php in your Laravel app.
  2. Add 'triage' => AsDecision::of(Triage::class) to the model's casts() method, with a JSON column named triage.
  3. Assign the result with $ticket->triage = $laya->decide($ticket->body, Triage::class); and call $ticket->save();.
  4. Read a field back with $ticket->triage->department; to confirm it returns the enum case.

Prompt for your agent

In the marcreichel/laya-php repo, add an AsDecision cast for <decision class> on the <model> model's <json column>. Save one decision, reload the model and report the stored JSON and the read-back enum value. Verify that assigning a non-decision value throws InvalidDecisionCastException.

Caveat. Null attributes are stored as null, and lists and floats round-trip, but a JSON value with a missing key or an unknown enum value throws an exception.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page