Weave Code
Filter Via Dot Access Data Laravel Package
consolidation/filter-via-dot-access-data
Filter nested PHP arrays with concise dot-access paths. This lightweight package lets you query config-like data using readable dotted keys, simplifying conditional filtering and value lookup in Laravel or plain PHP projects without verbose array access. Ideal for configuration, request data, and ne...
Filter data via dot-access data is a small utility that narrows arrays or objects down to the keys you actually need, using Laravel-style dot notation (e.g. user.profile.name) instead of manual nested isset() checks. Built on dflydev/dot-access-data, it resolves deep keys safely and skips missing paths without errors.
It fits neatly into Laravel/PHP projects that pass around large configuration or request payloads and want a clean, dependency-light way to extract subsets.
- Filter nested arrays or objects with intuitive dot-notation keys
- Silently ignore missing paths instead of throwing errors
- Works with plain PHP arrays and objects alike
- Zero configuration—drop in and call
- Pairs well with Laravel Zero and Termwind tooling
Frequently asked questions about Filter Via Dot Access Data
- What is consolidation/filter-via-dot-access-data used for?
- It is a small CLI-output filtering utility that lets you select array and object data using dot-notation paths, similar to a reverse data_get. It is built on dflydev/dot-access-data and can match keys, nested values, and wildcard paths so commands can output only the fields a user requests. It is not a Laravel framework package and has no service provider, facade, config, or Eloquent integration. Treat it as an optional developer utility for Artisan commands and internal CLI tools.
- How do I install consolidation/filter-via-dot-access-data in a Laravel project?
- Install it with Composer using composer require consolidation/filter-via-dot-access-data, then confirm that PHP and dflydev/dot-access-data constraints resolve against your Laravel version. There is no Laravel auto-discovery wiring to configure because the package provides no framework integration. Pin an exact version and test the dependency-resolution result in CI before adopting it. Add it only when a specific CLI or Artisan output-filtering use case justifies the dependency.
- Is consolidation/filter-via-dot-access-data compatible with Laravel 10 and Laravel 11?
- There are no explicit Laravel framework constraints because this is not a Laravel-specific package. Compatibility depends mainly on your PHP version and the dflydev/dot-access-data dependency resolving correctly. The last release was in January 2019, so you should run a Composer spike against your exact Laravel and PHP matrix rather than assuming support. If resolution or runtime behavior fails, use native Laravel helpers or an internal adapter instead.
- Does this package work with PHP 8.1, 8.2, and 8.3?
- PHP 8.1, 8.2, and 8.3 support is not guaranteed by the package metadata or maintenance history. Because the package is effectively unmaintained and last released in 2019, test it against each PHP version used in production and CI. Check for deprecations, missing-path behavior, and transitive dependency constraints during that spike. If issues appear, avoid direct reliance and implement the small filtering behavior natively.
- How is dot-notation filtering different from Laravel data_get or Arr::get?
- Laravel data_get and Arr::get retrieve values from arrays or objects using dot paths, while this package focuses on filtering CLI output by matching keys, nested values, or wildcards and extracting selected data. The overlap is significant, so simple field projection can often be handled with native Laravel helpers. Use this package only when its filtering and wildcard behavior clearly saves more effort than a small internal helper. Do not introduce it into controllers, API resources, domain services, or shared business logic.
- What happens when a dot path is missing or malformed in consolidation/filter-via-dot-access-data?
- Missing-key behavior and malformed dot paths should be characterized with tests before relying on the package in a command. The assessment flags missing paths, malformed paths, and type assumptions as possible causes of incorrect CLI output or command failures. Validate user-supplied paths and decide explicitly whether missing fields should be ignored, reported, or treated as errors. Isolating calls behind an application-owned adapter makes that behavior easier to control and replace.
- Can it filter nested arrays, objects, scalars, and wildcard paths?
- The package is intended for filtering arrays and objects by dot-notation paths and for matching nested values or wildcards. Its handling of scalars, deeply nested objects, and edge-case wildcard combinations should still be verified with characterization tests. Do not assume deterministic behavior without checking the exact inputs your Artisan command will receive. Keep usage limited to CLI output projection where incorrect filtering is low-risk and easy to detect.
- Is consolidation/filter-via-dot-access-data maintained and safe for production?
- It is effectively unmaintained relative to value: the last release was January 2019, the repository is unknown in the assessment, stars are low, and the license is reported as NOASSERTION. Security exposure is likely low for in-process CLI output filtering, but abandonment, PHP compatibility, and output-handling bugs remain real risks. Do not treat it as a platform capability or adopt it by default. Require a documented CLI use case, a compatibility spike, legal approval, and a fallback plan.
- What license does consolidation/filter-via-dot-access-data use, and can I use it commercially?
- The license is reported as NOASSERTION, which creates legal and procurement ambiguity. Do not assume it is MIT or another permissive license without confirming the actual repository and Composer metadata. Obtain legal approval before using it in production or distributing it as part of an application. If the license cannot be resolved, avoid the dependency and use native helpers or an internal implementation.
- What are alternatives to consolidation/filter-via-dot-access-data for Artisan command output?
- Use Laravel Arr::get, data_get, Collection methods, or a small application-owned helper when you only need basic dot-path selection. You can also evaluate dflydev/dot-access-data directly, but that inherits the same maintenance and compatibility concerns. If the package is already present transitively, isolate it behind an adapter and consider removing direct reliance. For most Laravel products, native helpers are the safer default unless a specific CLI filtering workflow needs wildcard behavior.
Weaver
How can I help you explore Laravel packages today?