Decimal Mutators Laravel Package

Getting Started

• Install/update with Composer and confirm Laravel/PHP version compatibility from the package README.
• Look first at the 1.1.0 changelog, README usage section, and the source file containing the new static mutator toggle. Verify the exact property name and default value before relying on it.
• First use case: temporarily disable mutators during bulk imports, seeders, legacy data syncs, or repair commands where you need to write/read raw attribute values without model mutation logic.

Implementation Patterns

• Use the static toggle at the narrowest possible scope: enable/disable around the operation, then restore the previous value in a finally block.
• Prefer wrapping the toggle in a small helper or service method so application code does not scatter direct static property writes.
• For queued jobs and Artisan commands, set the toggle at the start of the job/command and restore it before exit.
• In tests, cover both paths: normal mutator behavior and disabled-mutator behavior. Add a regression test for the “some fixes” in 1.1.0 if the changelog identifies affected behavior.
• If the package exposes configuration for mutators, decide whether config or the static property is the source of truth and document that choice for the team.

Gotchas and Tips

• A static mutator toggle is process-wide. Long-running workers, queue consumers, and Octane can leak the disabled state into later requests/jobs if you do not restore it.
• The release note says “static propriety”; verify the actual property name, visibility, and accepted values in source rather than guessing from the typo.
• Static state does not cross PHP processes. Disabling mutators in one command will not affect a separate web request or worker process.
• Confirm whether the toggle disables only mutators or also affects casts/accessors. Test the exact model behavior before using it in critical write paths.
• The unspecified fixes in 1.1.0 are a prompt to run the full test suite after upgrading, especially around mass assignment, casts, and model save/update flows.
• For debugging, use tinker or a focused test to inspect the static property before and after the operation, and log the restored state in jobs/commands.