Package Home

Zend Framework 2 Documentation (Manual)

PHK Home

File: /modules/zend.stdlib.hydrator.namingstrategy.mapnamingstrategy.html

Size:9873
Storage flags:no_autoload,compress/gzip (30%)

MapNamingStrategy — Zend Framework 2 2.4.2 documentation

MapNamingStrategy

Zend\Stdlib\Hydrator\NamingStrategy\MapNamingStrategy Maps keys based on a given map.

Example Usage

<?php
$namingStrategy = new \Zend\Stdlib\Hydrator\NamingStrategy\MapNamingStrategy([
    'foo' => 'bar',
    'baz' => 'bash'
]);
echo $namingStrategy->hydrate('foo'); // outputs: foo
echo $namingStrategy->hydrate('baz'); // outputs: bash

echo $namingStrategy->extract('bar'); // outputs: foo
echo $namingStrategy->extract('bash'); // outputs: baz
?>

This strategy can be used in hydrators to dictate how keys should be mapped:

<?php
class Foo {
    public $bar;
}

$namingStrategy = new \Zend\Stdlib\Hydrator\NamingStrategy\MapNamingStrategy([
    'foo' => 'bar',
    'baz' => 'bash'
]);
$hydrator = new \Zend\Stdlib\Hydrator\ObjectProperty();
$hydrator->setNamingStrategy($namingStrategy);

$foo = new Foo();
$hydrator->hydrate(['foo' => 123],$foo);

print_r($foo); // Foo Object ( [bar] => 123 )
print_r($hydrator->extract($foo)); // Array ( [foo] => 123 )
?>

Table Of Contents

Previous topic

IdentityNamingStrategy

Next topic

UnderscoreNamingStrategy

This Page

Note: You need to stay logged into your GitHub account to contribute to the documentation.

Edit this document

Edit this document

The source code of this file is hosted on GitHub. Everyone can update and fix errors in this document with few clicks - no downloads needed.

  1. Login with your GitHub account.
  2. Go to MapNamingStrategy on GitHub.
  3. Edit file contents using GitHub's text editor in your web browser
  4. Fill in the Commit message text box at the end of the page telling why you did the changes. Press Propose file change button next to it when done.
  5. On Send a pull request page you don't need to fill in text anymore. Just press Send pull request button.
  6. Your changes are now queued for review under project's Pull requests tab on GitHub.

For more information about the PHK package format: http://phk.tekwire.net