YiiFunctions - Helper file, a collections of Yii function to make the Yii coding shorten Follow @yiiframework

For params you could use something like that:

/**
 * Access array elements via dot notation
 * @param string $path
 * @param mixed[] $arr
 * @return mixed
 */
function dotToArray($path, &$arr)
{
 
    $parts = explode('.', $path);
    $path = & $arr;
 
    foreach($parts as $e)
    {
        $path = & $path[$e];
    }
    return $path;
}

I use shortcut functions mostly in views, here are only ones I use:

• app() - instance of application
• user() - returns Yii::app()->user->model, not Yii::app()->user
• tx() - for translations, with different params order, as most of the time I don't use $category
• msnippet() - function to get common configuration snippets, for grids, buttons etc.

Here is msnippet() if anyone interested:

/**
 * Get frequently used snippet.
 * snippetId should start with module name, or app for main snippets.
 * If started with dot '.' uses current module
 * @example app.some.config.value, content.editor.toolbar.lists, .editor.toolbar.lists
 * @staticvar mixed[] $snippets
 * @param string $snippetId
 * @return mixed
 */
function msnippet($snippetId)
{
    static $snippets = [];
    $parts = explode('.', $snippetId);
    $module = array_shift($parts);
    if(!$module)
    {
        $module = Yii::app()->controller->module->id;
        $snippetId = sprintf('%s%s', $module, $snippetId);
    }
 
    if(!isset($snippets[$module]))
    {
        if($module == 'app')
        {
 
            $snippets[$module] = require sprintf('%s/../config/snippets.cfg.php', dirname(__FILE__), $module);
        }
        else
        {
            $snippets[$module] = require sprintf('%s/%s/config/snippets.cfg.php', Yii::app()->modulePath, $module);
        }
    }
    return dotToArray($snippetId, $snippets);
}

with 'templates' feature. In my case, I had my IDE convert 'user' to 'Yii::app()->user->' with the flick of a tab key press (just to give an example. I use several of these for commonly used constructs). I second the reasons sounded by Jmper against the approach demonstrated in this article.

I used similar helper file in one of my first yii projects. Soon I discovered it brings more trouble than advantages.
First, you have to learn another layer of functions that actually bring nothing new to your application, just make the code shorter (well, not always - how shorter it is to write webapp() instead of Yii::app()? Exactly 2 characters).
Next, you have to remember for which functions you have shortcuts, and can use them, and for which not. I found myself easily forgetting and sometimes using shortcuts, sometimes the originals, causing a bit of mess in the code. Finally, for others who view and try to comprehend your code, and who know nothing about your convention, the code becomes harder to understand; they have to waste time before they discover the new functions and learn what they are for.
Perhaps the trick with parameters is interesting and worth implementing (this is the only part that brings something new and innovative); but only if you really have a lot of complex params in your project and use them often.