Dict Laravel Package

Product Decisions This Supports

• Improved Code Clarity & Maintainability: Replace raw arrays with a structured Dict class to enforce explicit intent (e.g., dict->get('key') vs. $array['key']), reducing ambiguity and bugs in associative data handling.
• Configuration Management: Standardize configuration bags (e.g., app settings, feature flags) with type-safe access, defaults, and merging utilities to simplify runtime overrides.
• Attribute Stores: Model dynamic entity attributes (e.g., user metadata, plugin options) with a consistent API for CRUD operations, reducing boilerplate.
• Bulk Operations: Leverage built-in methods for merging, updating, or filtering dictionaries to streamline data transformations (e.g., merging user preferences with defaults).
• Collection Consistency: Align with Laravel’s Collection patterns for iteration and chaining, easing adoption for teams familiar with Laravel’s ecosystem.
• Build vs. Buy: Avoid reinventing dictionary abstractions (e.g., custom classes or array wrappers) when this package offers a lightweight, battle-tested solution.
• Roadmap Alignment: Prioritize adoption if the team is migrating to PHP 8.2+ (for typed properties) or adopting stricter type safety in Laravel applications.

When to Consider This Package

• Adopt if:

  • Your codebase relies heavily on raw arrays for associative data but lacks consistency (e.g., mixed isset()/?? patterns).
  • You need a lightweight alternative to Laravel’s Collection for simple key-value operations (lower overhead than full collections).
  • Configuration or attribute management is fragmented across arrays/objects, and you want a unified API.
  • Your team values explicit intent over implicit array access (e.g., dict->set('key', $value) vs. $array['key'] = $value).
  • You’re using PHP 8.2+ and want to leverage typed properties without heavy frameworks like Symfony’s Component\OptionsResolver.

• Look elsewhere if:

  • You need advanced collection features (e.g., complex aggregations, lazy loading) → Use Laravel’s Collection or Illuminate\Support\Enumerable.
  • Your use case requires immutability or functional programming patterns → Consider spatie/array-to-object or league/arrayobjects.
  • Performance is critical for high-frequency operations (microbenchmarks may show array access is faster for simple cases).
  • You’re already using a dedicated config package (e.g., Laravel’s Config facade) that handles merging/validation natively.
  • The team prefers native PHP arrays for flexibility and no additional abstraction overhead.

How to Pitch It (Stakeholders)

For Executives:

"This package lets us write cleaner, more maintainable PHP code by replacing raw arrays with a structured dictionary class. For example, instead of scattered isset() checks or ?? operators, we’d use dict->get('key', default)—reducing bugs and improving readability. It’s especially valuable for configuration management and dynamic data stores, where consistency saves time. With minimal overhead (MIT-licensed, ~20 lines of code), it’s a low-risk way to standardize how we handle associative data across the app."

For Engineering:

*"php-standard-library/dict gives us a thin, Laravel-friendly wrapper for arrays with:

• Type-safe access: get(), set(), has() methods with defaults (no more isset() spaghetti).
• Bulk operations: Merge, update, or filter dictionaries in one call (e.g., dict->merge($overrides)).
• Iteration support: Works seamlessly with foreach and collection-style loops.
• Zero dependencies: Just drop it into Laravel or plain PHP.

Use cases:

• Replace raw arrays in config files or feature flags.
• Standardize attribute stores (e.g., user metadata, plugin settings).
• Simplify data transformations where merging/updating is common.

Tradeoffs:

• Slightly slower than raw arrays (but negligible for most use cases).
• Not a replacement for Laravel’s Collection—this is for simple key-value needs.

Proposal: Pilot it in one module (e.g., config management) to measure readability gains before rolling out broadly."*