Github url

laravel-ide-helper

by barryvdh

Laravel IDE Helper

10.2K Stars 913 Forks Last release: 3 months ago (v2.7.0) MIT License 674 Commits 75 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Laravel IDE Helper Generator

Latest Version on PackagistSoftware LicenseBuild StatusTotal Downloads

Complete PHPDocs, directly from the source

This package generates helper files that enable your IDE to provide accurate autocompletion. Generation is done based on the files in your project, so they are always up-to-date.

Installation

Require this package with composer using the following command:

composer require --dev barryvdh/laravel-ide-helper

This package makes use of Laravels package auto-discovery mechanism, which means if you don't install dev dependencies in production, it also won't be loaded.

If for some reason you want manually control this: - add the package to the

extra.laravel.dont-discover

key in

composer.json

, e.g.

json "extra": { "laravel": { "dont-discover": ["barryvdh/laravel-ide-helper",] } }
  • Add the following class to the
    providers
    array in
    config/app.php
    :
    php Barryvdh\LaravelIdeHelper\IdeHelperServiceProvider::class,
    If you want to manually load it only in non-production environments, instead you can add this to your
    AppServiceProvider
    with the
    register()
    method:
    php public function register() { if ($this-\>app-\>environment() !== 'production') { $this-\>app-\>register(\Barryvdh\LaravelIdeHelper\IdeHelperServiceProvider::class); } // ... }

Note: Avoid caching the configuration in your development environment, it may cause issues after installing this package; respectively clear the cache beforehand via

php artisan cache:clear

if you encounter problems when running the commands

Usage

Check out this Laracasts video for a quick introduction/explanation!

Note: You do need CodeComplice for Sublime Text: https://github.com/spectacles/CodeComplice

Automatic PHPDoc generation for Laravel Facades

You can now re-generate the docs yourself (for future updates)

php artisan ide-helper:generate

Note:

bootstrap/compiled.php

has to be cleared first, so run

php artisan clear-compiled

before generating.

This will generate the file

\_ide\_helper.php

which is expected to be additionally parsed by your IDE for autocomplete. You can use the config

filename

to change its name.

You can configure your

composer.json

to do this each time you update your dependencies:

"scripts": { "post-update-cmd": ["Illuminate\\Foundation\\ComposerScripts::postUpdate", "@php artisan ide-helper:generate", "@php artisan ide-helper:meta"] },

You can also publish the config file to change implementations (ie. interface to specific class) or set defaults for

--helpers

.

php artisan vendor:publish --provider="Barryvdh\LaravelIdeHelper\IdeHelperServiceProvider" --tag=config

The generator tries to identify the real class, but if it cannot be found, you can define it in the config file.

Some classes need a working database connection. If you do not have a default working connection, some facades will not be included. You can use an in-memory SQLite driver by adding the

-M

option.

You can choose to include helper files. This is not enabled by default, but you can override it with the

--helpers (-H)

option. The

Illuminate/Support/helpers.php

is already set up, but you can add/remove your own files in the config file.

Automatic PHPDocs for models

If you don't want to write your properties yourself, you can use the command

php artisan ide-helper:models

to generate PHPDocs, based on table columns, relations and getters/setters.

Note: this command requires a working database connection to introspect the table of each model

By default, you are asked to overwrite or write to a separate file (

\_ide\_helper\_models.php

). You can write the comments directly to your Model file, using the

--write (-W)

option, or force to not write with

--nowrite (-N)

.

Please make sure to back up your models, before writing the info.

Writing to the models should keep the existing comments and only append new properties/methods. The existing PHPDoc is replaced, or added if not found. With the

--reset (-R)

option, the existing PHPDocs are ignored, and only the newly found columns/relations are saved as PHPDocs.

php artisan ide-helper:models Post
/\*\* \* App\Models\Post \* \* @property integer $id \* @property integer $author\_id \* @property string $title \* @property string $text \* @property \Illuminate\Support\Carbon $created\_at \* @property \Illuminate\Support\Carbon $updated\_at \* @property-read \User $author \* @property-read \Illuminate\Database\Eloquent\Collection|\Comment[] $comments \* @method static \Illuminate\Database\Eloquent\Builder|\App\Models\Post newModelQuery() \* @method static \Illuminate\Database\Eloquent\Builder|\App\Models\Post newQuery() \* @method static \Illuminate\Database\Eloquent\Builder|\App\Models\Post query() \* @method static \Illuminate\Database\Eloquent\Builder|\App\Models\Post whereTitle($value) \* … \*/

By default, models in

app/models

are scanned. The optional argument tells what models to use (also outside app/models).

php artisan ide-helper:models Post User

You can also scan a different directory, using the

--dir

option (relative from the base path):

php artisan ide-helper:models --dir="path/to/models" --dir="app/src/Model"

You can publish the config file (

php artisan vendor:publish

) and set the default directories.

Models can be ignored using the

--ignore (-I)

option

php artisan ide-helper:models --ignore="Post,User"

Or can be ignored by setting the

ignored\_models

config

'ignored\_models' =\> [Post::class, Api\User::class],

Note: With namespaces, wrap your model name in double-quotes (

"

):

php artisan ide-helper:models "API\User"

, or escape the slashes (

Api\\User

).

Magic

where\*

methods

Eloquent allows calling

where<attribute></attribute>

on your modes, e.g.

Post::whereTitle(…)

and automatically translates this to e.g.

Post::where('title', '=', '…')

.

If for some reason it's undesired to have them generated (one for each column), you can disable this via config

write\_model\_magic\_where

and setting it to

false

.

Magic

\*\_count

properties

You may use the [

::withCount

](https://laravel.com/docs/master/eloquent-relationships#counting-related-models) method to count the number results from a relationship without actually loading them. Those results are then placed in attributes following the

<columname>_count</columname>

convention.

By default, these attributes are generated in the phpdoc. You can turn them off by setting the config

write\_model\_relation\_count\_properties

to

false

.

Unsupported or custom database types

Common column types (e.g. varchar, integer) are correctly mapped to PHP types (

string

,

int

).

But sometimes you may want to use custom column types in your database like

geography

,

jsonb

,

citext

,

bit

, etc. which may throw an "Unknown database type"-Exception.

For those special cases, you can map them via the config

custom\_db\_types

. Example:

php 'custom\_db\_types' =\> ['mysql' =\> [ 'geography' =\> 'array', 'point' =\> 'array',], 'postgresql' =\> ['jsonb' =\> 'string', '\_int4' =\> 'array',], ],

Automatic PHPDocs generation for Laravel Fluent methods

If you need PHPDocs support for Fluent methods in migration, for example

$table-\>string("somestring")-\>nullable()-\>index();

After publishing vendor, simply change the

include\_fluent

line your

config/ide-helper.php

file into:

'include\_fluent' =\> true,

Then run

php artisan ide-helper:generate

, you will now see all Fluent methods recognized by your IDE.

Auto-completion for factory builders

If you would like the

factory()-\>create()

and

factory()-\>make()

methods to return the correct model class, you can enable custom factory builders with the

include\_factory\_builders

line your

config/ide-helper.php

file.

'include\_factory\_builders' =\> true,

For this to work, you must also publish the PhpStorm Meta file (see below).

PhpStorm Meta for Container instances

It's possible to generate a PhpStorm meta file to add support for factory design pattern. For Laravel, this means we can make PhpStorm understand what kind of object we are resolving from the IoC Container. For example,

events

will return an

Illuminate\Events\Dispatcher

object, so with the meta file you can call

app('events')

and it will autocomplete the Dispatcher methods.

php artisan ide-helper:meta
app('events')-\>fire(); \App::make('events')-\>fire(); /\*\* @var \Illuminate\Foundation\Application $app \*/ $app-\>make('events')-\>fire(); // When the key is not found, it uses the argument as class name app('App\SomeClass'); // Also works with app(App\SomeClass::class);

Note: You might need to restart PhpStorm and make sure

.phpstorm.meta.php

is indexed.

Note: When you receive a FatalException: class not found, check your config (for example, remove S3 as cloud driver when you don't have S3 configured. Remove Redis ServiceProvider when you don't use it).

You can change the generated filename via the config

meta\_filename

. This can be useful for cases you want to take advantage the PhpStorm also supports the directory

.phpstorm.meta.php/

which would parse any file places there, should your want provide additional files to PhpStorm.

Usage with Lumen

This package is focused on Laravel development, but it can also be used in Lumen with some workarounds. Because Lumen works a little different, as it is like a bare bone version of Laravel and the main configuration parameters are instead located in

bootstrap/app.php

, some alterations must be made.

Enabling Facades

While Laravel IDE Helper can generate automatically default Facades for code hinting, Lumen doesn't come with Facades activated. If you plan in using them, you must enable them under the

Create The Application

section, uncommenting this line:

// $app-\>withFacades();

From there, you should be able to use the

create\_alias()

function to add additional Facades into your application.

Adding the Service Provider

You can install Laravel IDE Helper in

app/Providers/AppServiceProvider.php

, and uncommenting this line that registers the App Service Providers, so it can properly load.

// $app-\>register(App\Providers\AppServiceProvider::class);

If you are not using that line, that is usually handy to manage gracefully multiple Laravel/Lumen installations, you will have to add this line of code under the

Register Service Providers

section of your

bootstrap/app.php

.

if ($app-\>environment() !== 'production') { $app-\>register(\Barryvdh\LaravelIdeHelper\IdeHelperServiceProvider::class); }

After that, Laravel IDE Helper should work correctly. During the generation process, the script may throw exceptions saying that some Class(s) doesn't exist or there are some undefined indexes. This is normal, as Lumen has some default packages stripped away, like Cookies, Storage and Session. If you plan to add these packages, you will have to add them manually and create additional Facades if needed.

Adding Additional Facades

Currently, Lumen IDE Helper doesn't take into account additional Facades created under

bootstrap/app.php

using

create\_alias()

, so you need to create a

config/app.php

file and add your custom aliases under an

aliases

array again, like so:

return ['aliases' =\> [ 'CustomAliasOne' =\> Example\Support\Facades\CustomAliasOne::class, 'CustomAliasTwo' =\> Example\Support\Facades\CustomAliasTwo::class, //...] ];

After you run

php artisan ide-helper:generate

, it's recommended (but not mandatory) to rename

config/app.php

to something else, until you have to re-generate the docs or after passing to production environment. Lumen 5.1+ will read this file for configuration parameters if it is present, and may overlap some configurations if it is completely populated.

License

The Laravel IDE Helper Generator is open-sourced software licensed under the MIT license

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.