定制 daveismyname/laravel-filters 二次开发

按需修改功能、优化性能、对接业务系统,提供一站式技术支持

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

daveismyname/laravel-filters

Composer 安装命令:

composer require daveismyname/laravel-filters

包简介

Save and reuse query string based filters

README 文档

README

A Laravel package for saving and reusing query based filtering.

Installation

Via Composer

$ composer require dcblogdev/laravel-filters

In Laravel 5.5 the service provider will automatically get registered. In older versions of the framework just add the service provider in config/app.php file:

'providers' => [
    // ...
    Dcblogdev\Filters\FiltersServiceProvider::class,
];

You can publish the migration with:

php artisan vendor:publish --provider="Dcblogdev\Filters\FiltersServiceProvider" --tag="migrations"

After the migration has been published migrate it:

php artisan migrate

You can publish the config file with:

php artisan vendor:publish --provider="Dcblogdev\Filters\FiltersServiceProvider" --tag="config"

When published, the config/filters.php config file contains:

<?php

return [

    
];

Model

Access filter model, to access the model reference this ORM model

use Dcblogdev\Filters\Models\Filter;

Usage

Note this package expects a user to be logged in.

A routes example:

Route::group(['middleware' => ['web', 'auth']], function(){
    Route::get('demo', function(){
        $filters = Filters::get();

        return view('demo');
    });
});

the get accepts 2 optional params:

  1. The name of the module/section ie users
  2. The relative url to redirect to ie /admin/users

In demo.blade.php view:

Save a filter:

<form method="get">
    <div class="control-group">
        <label for='savedfilter'>Use a saved filter:</label>
        <select name='savedfilter' id="savedfilter" class='form-control' onchange="this.form.submit()">
        <option value=''>Select</option>
        @if ($filters)
            @foreach($filters as $filter)
                <option value='{{ $filter->id }}'>{{ $filter->title }}</option>
            @endforeach
        @endif
        </select>
    </div>
</form>

Remove a filter

<form method="get">
    <div class="control-group">
        <label for='removefilter'>Remove a saved filter:</label>
        <select name='removefilter' id="removefilter" class='form-control' onchange="this.form.submit()">
        <option value=''>Select</option>
        @if ($filters)
            @foreach($filters as $filter)
                <option value='{{ $filter->id }}'>{{ $filter->title }}</option>
            @endforeach
        @endif
        </select>
    </div>
</form>

Store a new filter

<form method="get">
    <div class="control-group">
        <label for='filterTitle'>Save filter:</label>
        <input class='form-control' id='filterTitle' type="text" name="filterTitle" value="" />
    </div>

    <div class="control-group">
        <br><button type="submit" id='savefilter' class="btn btn-success" name="savefilter"><i class="fa fa-check"></i> Save Filter</button>
    </div>
</form>

For the filter actions to run call run($module, $url)

Filters::run('users', 'admin/users');

Internally there are 3 methods that will be called based on the query string parameters:

When savefilter exists in the url then storeFilter() will run to store the filter. Also storeFilter requires a filterTitle parameter to give a name to the filter.

When savedfilter exists in the url then applyFilter() will return the filter stored. When removefilter exists in the url then deleteFilter() will run to delete the filter.

Change log

Please see the changelog for more information on what has changed recently.

Contributing

Contributions are welcome and will be fully credited.

Contributions are accepted via Pull Requests on Github.

Pull Requests

  • Document any change in behaviour - Make sure the readme.md and any other relevant documentation are kept up-to-date.

  • Consider our release cycle - We try to follow SemVer v2.0.0. Randomly breaking public APIs is not an option.

  • One pull request per feature - If you want to do more than one thing, send multiple pull requests.

Security

If you discover any security related issues, please email dave@daveismyname.com email instead of using the issue tracker.

License

license. Please see the license file for more information.

daveismyname/laravel-filters 适用场景与选型建议

daveismyname/laravel-filters 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 62.51k 次下载、GitHub Stars 达 9, 最近一次更新时间为 2019 年 02 月 27 日, 在 PHP 生态内属于活跃度较高的组件。

它主要适用于以下技术方向: 「filter」 「laravel」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。

我们在过去多个企业项目中使用过 daveismyname/laravel-filters 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。

围绕 daveismyname/laravel-filters 我们能提供哪些服务?
定制开发 / 二次开发

基于 daveismyname/laravel-filters 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。

BUG 修复 & 性能优化

线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。

项目外包 & 长期维护

承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。

yvsm@zunyunkeji.com QQ:316430983 微信:yvsm316 西安尊云信息科技 · 专注 PHP / Go / 分布式系统研发

统计信息

  • 总下载量: 62.51k
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 9
  • 点击次数: 15
  • 依赖项目数: 0
  • 推荐数: 0

GitHub 信息

  • Stars: 9
  • Watchers: 2
  • Forks: 2
  • 开发语言: PHP

其他信息

  • 授权协议: MIT
  • 更新时间: 2019-02-27