laravel-enso / datatable Goto Github PK

php artisan vendor:publish --tag=datatable-component

[Symfony\Component\Debug\Exception\FatalThrowableError]
Class 'LaravelEnso\DataTable\DataServiceProvider' not found

I have verified the folder is in the vendor directory

We want to specify what buttons / actions to display by default.

Analyzing if this makes sense

update DT documentation for the meta-icon option, and cfg icon array

It would be nice if you offer an option to filter individual columns like described here:
https://datatables.net/examples/api/multi_filter_select.html

Maybe you can give me an advice where to implement it and I'll try to add the funcunality?

Hi
I have implemented the data table. Also have added the meta tag "searchable" for the columns. but the search box doesn't appear. I checked the documentation and couldn't find anything related to search bar .

The following is my template.json file . Please let me know what i'm missing here so that i can enable the search bar on top on the table as shown in the examples.

{
   "routePrefix": "table",
    

    "crtNo": true,
    "cache": false,
    "flatten": false,
    "auth": false,
    "debounce": 100,
    "lengthMenu": [10, 15, 20, 25, 30],
     "selectable": false,

    "comparisonOperator": "LIKE",
       "columns": [
        {
            "label": "name",
            "data": "table.name",
            "name": "name",
            "meta": ["searchable", "sortable"]
       }
]
}
           

'appends' will allow to use the laravel accessors in the returned result

Debounce for getData() not working correctly when we have more than one component with custom filters.

Update documentation for newly introduced abstraction layer.

Ref #86b19f2f61f8edf3dc8c4a76b86582db9d19daba

Hi,

Will be very useful to allow not only pass a raw query to this package else to be able to pass a json, in order to load data from external api integration (mailchimp, github, and so on).

That will give to this package a powerful integration with the enso admin-panel.

I did a test with a rest api that I have developed. It worked, if I overwrite the method public function getTableData() on the trait use LaravelEnso\DataTable\app\Traits\DataTable;

tableController.php

public function getTableData()
    {
        $client = new Client(['base_uri' => env('API_HOST')]);

        $ApiAuthorization = ['headers' => [
            'X-Authorization'=> 'xxxxxxxx'
        ], 'http_errors' => true];

        $response = $client->request('GET', 'my-endpoint', $ApiAuthorization);
       
        // The response already contains the fields needed for the package to create the table. The 
        // response return exactly the same as the raw query does. 
        return response()->json(json_decode($response->getBody()));
    }

Something did not worked for me when I tested it passing a filter for search. I tried to return exactly what was expected but I realised I was missing something else. I have not try any further but seems like its possible to integrate it.

Regarding to search some challenges will show up for sure, since there is no sql at all. But maybe could be fixed by filtering array of collections and using transformers for formating the right json response.

Mihai we need to cover this feature in the docs.

John you should update the snippet :)

It would be nice to get a config option to set the decimal separator for excel export.

I got an exception after creating a new locale "DataTables language file is missing for $locale". This issue is affecting the datatable rendering. I can see that the file is missing on the folder "dt-lang", but the record is created on the table language.

vendor/laravel-enso/datatable/src/app/Classes/TableInit.php

the render function is called for every cell if the render array is defined.

It's not required

It would be nice if you can add the possibility to enable/disable extraFilters and intervalFilters.

Example:
[BUTTON: 2017]

• if enabled, query should be "... WHERE ... AND year = 2017 ..."
• if disabled, query should be "... WHERE ..."

It's time :)

Now the vue component generates a dynamic id for the table based on the _uid.

This causes a problem when we use the saveState option from DT library. The DT library saves the state for each table in the browsers cookie under a generated key that uses the table id.

This results in multiple cookie entries for the same table.