PHPackages                             nahid/presento - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. nahid/presento

ActiveLibrary[Utility &amp; Helpers](/categories/utility)

nahid/presento
==============

Presento is a package for PHP data presenter

v1.1.3(5y ago)747.2k6MITPHPPHP &gt;=7.0CI failing

Since Aug 25Pushed 5y ago5 watchersCompare

[ Source](https://github.com/nahid/presento)[ Packagist](https://packagist.org/packages/nahid/presento)[ RSS](/packages/nahid-presento/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (9)Dependencies (2)Versions (12)Used By (0)

Presento
========

[](#presento)

A data preparing and presenting package for PHP.

Why Presento?
-------------

[](#why-presento)

**Presento** is a simple but powerful tools for preparing and presenting data. When we build an API based application, we need to *transform* the data before *present* it through the response. This package will make this task easier for you.

Not clear enough?

Don't worry, you'll get better idea from the [Usage examples](#usage).

### Requirements

[](#requirements)

```
PHP >= 7.0
ext-json

```

Installation
------------

[](#installation)

Install the package using composer:

```
composer require nahid/presento

```

Usage
-----

[](#usage)

**Presento** serves two important purposes. one is **Presentation** and another is **Transformation** of the data.

Let's see some examples to understand how to use it.

We'll use the following data set to show the examples. Let's say we've this data set fetched from some data source and need to do some transformation or modifications before sending it to the response.

```
$response = [
    "id" => 123456,
    "name" => "Nahid Bin Azhar",
    "email" => "talk@nahid.im",
    "type" => 1,
    "is_active" => 1,
    "created_at" => "2018-01-02 02:03:04",
    "updated_at" => "2018-01-02 02:03:04",
    "deleted_at" => "2018-01-02 02:03:04",
    "projects" => [
        [
            "id" => 1,
            "name" => "Laravel Talk",
            "url"   => "https://github.com/nahid/talk",
            "license" => "CC0",
            "created_at" => "2016-02-02 02:03:04"
        ],
        [
            "id" => 2,
            "name" => "JsonQ",
            "url"   => "https://github.com/nahid/jsonq",
            "license" => "MIT",
            "created_at" => "2018-01-02 02:03:04"
        ]
    ]
];
```

#### Simple Presentation Example

[](#simple-presentation-example)

When sending this data to the API response, we only want to send the `id`, `name`, `email`, `type`, `is_active` and `projects`.

We can simply do that by preparing a Presenter for this like following.

```
// UserPresenter.php

class UserPresenter extends \Nahid\Presento\Presenter
{
    public function present() : array
    {
        return [
            'id',
            'name',
            'email',
            'type',
            'is_active',
            'projects',
        ];
    }
}
```

And you might already guessed how to use it, right?

```
$user = new UserPresenter($response);
dump($user->get());
```

It'd show something like this:

```
[
    "id" => 123456,
    "name" => "Nahid Bin Azhar",
    "email" => "talk@nahid.im",
    "type" => 1,
    "is_active" => 1,
    "projects" => [
        [
            "id" => 1,
            "name" => "Laravel Talk",
            "url"   => "https://github.com/nahid/talk",
            "license" => "CC0",
            "created_at" => "2016-02-02 02:03:04"
        ],
        [
            "id" => 2,
            "name" => "JsonQ",
            "url"   => "https://github.com/nahid/jsonq",
            "license" => "MIT",
            "created_at" => "2018-01-02 02:03:04"
        ]
    ]
]
```

Pretty simple, right?

#### 'key' aliasing in Presentation example

[](#key-aliasing-in-presentation-example)

Let's say you want to change some of the 'key' to something different, like the `id` key to `user_id` . How can you do that?

Just do the following.

```
// UserPresenter.php
class UserPresenter extends \Nahid\Presento\Presenter
{
    public function present() : array
    {
        return [
            'user_id' => 'id',
            'name',
            'email',
            'type',
            'is_active',
        ];
    }
}
```

This will format the data like following:

```
[
    "user_id" => 123456,
    "name" => "Nahid Bin Azhar",
    "email" => "talk@nahid.im",
    "type" => 1,
    "is_active" => 1,
]
```

#### Deep traversing in Presentation example

[](#deep-traversing-in-presentation-example)

You can easily dive deep and get data from a nested level by using `.` (dot) notation.

Let's say you want to show the `name` of the first package as the `top_package` in your data.

This is how you do it.

```
// UserPresenter.php
class UserPresenter extends \Nahid\Presento\Presenter
{
    public function present() : array
    {
        return [
            'id',
            'name',
            'email',
            'type',
            'is_active',
            'top_package' => 'projects.0.name',
            'projects',
        ];
    }
}
```

This will format the data like this:

```
[
    "id" => 123456,
    "name" => "Nahid Bin Azhar",
    "email" => "talk@nahid.im",
    "type" => 1,
    "is_active" => 1,
    "top_package" => "Laravel Talk",
    "projects" => [
        [
            "id" => 1,
            "name" => "Laravel Talk",
            "url"   => "https://github.com/nahid/talk",
            "license" => "CC0",
            "created_at" => "2016-02-02 02:03:04"
        ],
        [
            "id" => 2,
            "name" => "JsonQ",
            "url"   => "https://github.com/nahid/jsonq",
            "license" => "MIT",
            "created_at" => "2018-01-02 02:03:04"
        ]
    ]
]
```

Notice the `top_package` key in the data.

#### Simple Transformer Example

[](#simple-transformer-example)

Let's say our UserPresenter is like this:

```
// UserPresenter.php
class UserPresenter extends \Nahid\Presento\Presenter
{
    public function present() : array
    {
        return [
            'user_id' => 'id',
            'name',
            'email',
            'type',
            'is_active',
        ];
    }
}
```

And we want to show the `user_id` as *hashed* value instead of an incremental integer value as it is in our database. That means we want to transform the `user_id`.

To do that we need to create a Transformer Class like this:

```
// UserTransformer.php
class UserTransformer extends \Nahid\Presento\Transformer
{
    public function getUserIdProperty($value)
    {
        return md5($value);
    }
}
```

Notice that, as we will transform the `user_id` property, we named our transformer method as `getUserIdProperty`. So, if you want to transform the `name` property too, you need to just create another method in this class named `getNameProperty` and add the transformation logic inside it.

Now, we need to let know the *Presenter* how to *Transform* the data before presenting it.

To do that, we need to add the following method in the `UserPresenter` class.

```
// UserPresenter.php
public function transformer()
{
    return UserTransformer::class;
}
```

So, our final output would be:

```
[
    "user_id" => "e10adc3949ba59abbe56e057f20f883e",
    "name" => "Nahid Bin Azhar",
    "email" => "talk@nahid.im",
    "type" => 1,
    "is_active" => 1,
]
```

Ain't it easy, mate?

#### Nested Presenter Example

[](#nested-presenter-example)

You might notice that there is a collection of `projects` in our data set. If each `project` is a separate resource, you might have a separate Presenter for that. Like this:

```
// ProjectPresenter.php
class ProjectPresenter extends \Nahid\Presento\Presenter
{
    public function present() : array
    {
        return [
            'id',
            'name',
            'url',
            'license',
            'created_at',
        ];
    }

    public function transformer()
    {
        return ProjectTransformer::class;
    }
}
```

Can you use this Presenter for each of the `projects` in the *Users* data?

Hell Yeah! Just do this:

```
// UserPresenter.php
public function present() : array
{
    return [
        'user_id' => 'id',
        'name',
        'email',
        'type',
        'is_active',
        'projects' => [ProjectPresenter::class => ['projects']],
    ];
}
```

Now, each of the `project` in the list of `projects` in *Users* will be presented as defined in the `ProjectPresenter`.

#### Base Data format conversion Example

[](#base-data-format-conversion-example)

As you have seen that, the data set we have used till now is a plain *Array*. But some times it might not be the case. You might need to work with something different, like **Eloquent Model** of Laravel framework. In that case, you can simply add a method called `convert` in your *Presenter* to convert the Base data to an Array format.

Let's see an Example:

```
// UserPresenter.php
public function convert($data)
{
    if ($data instanceof Model) {
        return $data->toArray();
    }

    return $data;
}
```

That's it.

###  Health Score

35

—

LowBetter than 80% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity34

Limited adoption so far

Community15

Small or concentrated contributor base

Maturity60

Established project with proven stability

 Bus Factor1

Top contributor holds 72% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~34 days

Recently: every ~71 days

Total

11

Last Release

2121d ago

Major Versions

v0.0.2 → v1.0.02019-08-27

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/3167309?v=4)[Nahid Bin Azhar](/maintainers/nahid)[@nahid](https://github.com/nahid)

---

Top Contributors

[![nahid](https://avatars.githubusercontent.com/u/3167309?v=4)](https://github.com/nahid "nahid (36 commits)")[![me-shaon](https://avatars.githubusercontent.com/u/831997?v=4)](https://github.com/me-shaon "me-shaon (13 commits)")[![maki10](https://avatars.githubusercontent.com/u/13304146?v=4)](https://github.com/maki10 "maki10 (1 commits)")

---

Tags

arrayphpphp7presentertransformer

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/nahid-presento/health.svg)

```
[![Health](https://phpackages.com/badges/nahid-presento/health.svg)](https://phpackages.com/packages/nahid-presento)
```

###  Alternatives

[mervick/emojionearea

WYSIWYG-like EmojiOne Converter / Picker Plugin for jQuery

941207.3k5](/packages/mervick-emojionearea)[lisachenko/protocol-fcgi

Implementation of FCGI Protocol in PHP

126104.5k2](/packages/lisachenko-protocol-fcgi)[sdboyer/gliph

A graph library for PHP.

17029.1k1](/packages/sdboyer-gliph)[pragmarx/zipcode

A worldwide address-by-zipcode searcher.

10265.4k](/packages/pragmarx-zipcode)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
