2017 © Pedro Peláez
 

project laravel-flatfiles

Export and import flatfiles with Laravel like charm

image

real-media-technic-staudacher/laravel-flatfiles

Export and import flatfiles with Laravel like charm

  • Friday, May 4, 2018
  • by patriziotomato
  • Repository
  • 1 Watchers
  • 2 Stars
  • 1,026 Installations
  • PHP
  • 0 Dependents
  • 0 Suggesters
  • 1 Forks
  • 0 Open issues
  • 7 Versions
  • 24 % Grown

The README.md

Export Eloquent queries to flatfiles using simple configuration

TravisCI, (*1)

Installation

composer require real-media-technic-staudacher/laravel-flatfiles:^5.0

To overwrite the default configuration, (*2)

php artisan vendor:publish

Then select the option Provider: RealMediaTechnicStaudacher\LaravelFlatfiles\FlatfileExportServiceProvider. The default configuration looks like:, (*3)

return [
    'default' => env('FLATFILE_DRIVER', 'csv'),

    'drivers' => [
        'csv' => [
            'charset'               => 'UTF-8',
            'delimiter'             => ';',
            'enclosure'             => '"',
            'bom'                   => true,
            'force_enclosure'       => false,
            'ignore_sylk_exception' => false,
        ],
    ],
];

As you see, right now, only CSV exports are supported ;-), (*4)

Usage example / Basic workflow

// Implement FlatfileFields to define your export fields (See later sections for details)
class ExportJob implements ShouldQueue, FlatfileFields
{
    // FlatfileExporter magically find out, whether your auto-injecting method's class implement the FlatfileFields-interface!
    // If so, it use this field definition by default
    public function handle(FlatfileExport $flatfile, $exportFilepath = '/subfolderOnDisk/export.csv')
    {
        // Expose where to export the file. Based on file extension (ie. .csv) we select the proper exporter for you)
        $flatfile->to($exportFilepath, 'diskNameOrInstance');

        $flatfile->addHeader();

        // You may want to load any data globally to prevent database queries for each row or even cell
        $imagePaths = $this->imagepaths();

        // Only needed for very custom contents in your flatfile!
        $flatfile->beforeEachRow(function (Model $model) use ($imagePaths) {
            // Do some very special magic to make custom image paths available for your "cells" for
            // each row.
            // Typically here you merge the globally loaded objects with the data you need for you cell
            // $model here is an eloquent model selected by queryToSelectEachRow()
        });

        // Here we use a query builder (if you want to) and ensure to restrict memory usage by chunking
        $this->queryToSelectEachRow()->chunk(500, function ($chunk) use ($flatfile) {
            $flatfile->addRows($chunk);
        });

        // Dont forget to properly "close" the operation by this command
        $flatfile->moveToTarget();
    }

    // In your field definition to are supposed to "only" pick out loaded or prepared data instead of
    // doing complex calculations (See beforeEachRow())
    public function fields(): array {
        return []; // Your field definition
    }

    // Return an elequent query builder and carefully eager load relations you will gonna use in your cells!
    protected function queryToSelectEachRow() {
        return Products::whereCategory(15)->with('images');
    }
}

Load export

Easiest way is to auto-inject the FlatfileExport while implementing the FlatfileFields interface:, (*5)

// This will lookup for your field definition in the current class
class ExportJob implements ShouldQueue, FlatfileFields
{
    public function handle(FlatfileExport $flatfile) {}
}

If you want to use a dedicated class for field definitions are get the array from somewhere else use withFields(), (*6)

    public function handle(FlatfileExport $flatfile) {
        $flatfile->withFields($objImplementingFlatfileFields);

        // Alternatively you can resolve and assign fields in one step
        // app(FlatfileExport::class, [$objImplementingFlatfileFields]);
        // app(FlatfileExport::class, ['fields' => $objImplementingFlatfileFields]);
    }

Specify target file / location

Using filesystem disk

  • This enables you to export to all available filesystem drivers
  • Exports are generated locally/temporary first and than streamed to disk
    $flatfile->to('relative/path/to/file-with-extension.csv', Storage::disk('name'));

    // Do export ...

    $flatfile->moveToTarget();

Prepare global export resources

..., (*7)

Loop through data and write to export file

  • Preselect the models that will represent a single row in your flat file
  • Chunk through this result set to limit resources
    public function handle()
    {
        $flatfile = app(FlatfileExport::class, [$this]);
        $flatfile->to($this->csvFilepath, $this->disk);

        // Optionally add a Header
        $flatfile->addHeader();

        // Proposed way to step through a large result set
        $this->queryToSelectEachRow()->chunk(500, function ($chunk) use ($flatfile) {
            $flatfile->addRows($chunk);
        });
    }

    protected function queryToSelectEachRow(): Builder
    {
        return CampaignModels::whereCampaignId($this->campaignId)->with(['model.product', 'campaign']);
    }

Finish export

$flatfile->moveToTarget();

Define fields

Fields are defined within an object/class implementing the FlatfileFields interface, thus a public function field(). Implement this function directly in your export-handling class, or in a dedicated sort like a DTO class., (*8)

Why? You get the possiblity to add callbacks in your field definitions, so that you can define dynamic cells easily, (*9)

In your field() method you need to define an array of fields. This will generate a flatfile with one column each field array element., (*10)

Assume we load a collection of products having attributes named product_name. The definition looks like:, (*11)

    $fields = [
        'product_name' => 'Product Name'
    ];

The field defintions are pretty flexible. Better learn by examples by yourself, (*12)

    $fields = [
        'relation.columnOfRelation' => 'Column Header Label', // Relations should be eager loaded
        [
            'label'    => 'Label with special characters',
            'column'   => 'relation.columnOfRelation', // Value of param $value in callback (optional)
            'callback' => function ($model, $value) { // Format cell values
                return $model->currencySign.' '.number_format($value);
            }
        ],
        'attribute' => [ // Column name can also still be the key of the array
            'label'    => 'Label with special characters',
            'callback' => function ($model, $value) {}
        ],
        'Column header' => function() { // For callbacks the header label can also be specified in the key! Crazy...
            return 'static cell content';
        },
        'Empty cell' => '',
    ];

One row for each relation

If you have a relation you want to put into one row and preserve it's parent as one row if it hasn't a relation, you can use the following:, (*13)

    public function handle()
    {
        // ...

        // relation has to be loaded in items of course
        $items->each(function (Item $item) use ($export) {
          $export->addRowForEachRelation($item, ['relation', 'more.*.relations'], 'fieldAccessorAlias', true);
        });

        // ...
    }

    public function fields(): array
    {
        return [
            'fieldAccessorAlias.fieldName' => 'Output of relation fieldName if it is existing',
            'fieldAccessorAlias.fieldNameMoreRelations' => 'Output of more.*.relations fieldName if it is existing',
        ];
    }

SYLK file format error

By default, an exception getting thrown if the first column in the header row is named ID. Background for this is the SYLK formatting, which does not allow an flawless opening with Microsoft Excel in some Versions. You are free to disable the exception via the config drivers.csv.ignore_sylk_exception again., (*14)

Upgrade guide

To v3 from v2

  • Added return types. Also in interfaces. So mainly interfaces have to be checked: ie. public function fields(): array;. Tipp: Search for public function fields( across the whole project.
  • New Namespace. Change imports from LaravelFlatfiles\* to RealMediaTechnicStaudacher\LaravelFlatfiles\*
  • Changed order of callback paramters of field callback method to prevent $null in most of the calls function ($null, Asset $asset). Now: function (Asset $asset). Tipp: Search for function ($null and all function fields in your editor.

The Versions

04/05 2018

dev-master

9999999-dev

Export and import flatfiles with Laravel like charm

  Sources   Download

MIT

The Requires

 

The Development Requires

laravel framework export import os flatfile scoop

04/05 2018

v0.2.1

0.2.1.0

Export and import flatfiles with Laravel like charm

  Sources   Download

MIT

The Requires

 

The Development Requires

laravel framework export import os flatfile scoop

19/03 2018

v0.2.0

0.2.0.0

Export and import flatfiles with Laravel like charm

  Sources   Download

MIT

The Requires

 

The Development Requires

laravel framework export import os flatfile scoop

13/02 2018

dev-analysis-qBY3Q6

dev-analysis-qBY3Q6

Export and import flatfiles with Laravel like charm

  Sources   Download

MIT

The Requires

 

The Development Requires

laravel framework export import os flatfile scoop

13/02 2018

dev-laravel56

dev-laravel56

Export and import flatfiles with Laravel like charm

  Sources   Download

MIT

The Requires

 

The Development Requires

laravel framework export import os flatfile scoop

30/01 2018

dev-feature/SCOOPOS-175_test

dev-feature/SCOOPOS-175_test

Export and import flatfiles with Laravel like charm

  Sources   Download

MIT

The Requires

 

The Development Requires

laravel framework export import os flatfile scoop

07/12 2017

0.1.0

0.1.0.0

Export and import flatfiles with Laravel like charm

  Sources   Download

MIT

The Requires

 

laravel framework export import os flatfile scoop