Download the PHP package aviator/eloquent-search-map without Composer
On this page you can find all versions of the php package aviator/eloquent-search-map. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package eloquent-search-map
Overview
Add Eloquent query search constraints effortlessly with this Eloquent macro.
This is especially handy when you find yourself building simple, optional searches often:
With this package you can do this instead:
You may create an optional column map on your model, as well as mapping request properties on the fly.
Installation
Via Composer:
In your config/app.php add Aviator\Search\ServiceProvider::class to the providers array:
Testing
Via Composer:
Usage
Model Setup
To start, make the model you want to search implement the Searchable contract and use the SearchableTrait.
Then set a searches array property on your model containing your searchable columns. To search in the email column using $model::search(['email']):
To search in the email column using $model::search(['alias'])
Request Aliases
By default, the search builder assumes the column name or alias matches the request data. So if you call $model::search(['something']), it will look for request('something').
Of course you can specify the request property name manually:
This tells the search builder to look for the email request data in request('user_email') instead of the default.
Custom Requests
If you need to pass a custom request into the macro, use the second parameter, which accepts an object extending Illuminate\Http\Request:
Of course, this is completely optional. If a request isn't provided, it will be retrieved from the container.
Related Models
If you want to query related models, you can! Use dot notation:
This will look for a relation method called company() and add a whereHas constraint to the query. For instance:
This will look on the User model for a relation company() and search in the city attribute of that model.
By default we assume that the request will have the same property, snake cased. For the above query constraint the search builder will look for request('company_city').
This can also be mapped:
The search builder will now look for request('city') instead.
Other Stuff
License
This package is licensed with the MIT License (MIT).
