I like yoda for 3 === $foo (instead of $foo === 3), but I don't like yoda for 3 === \my_method().

The main reasons for yoda is to avoid accidental assignments which can not happen on method calls.

Is it possible to either only suggest yodo for variable comparisons or to make it configurable in which cases it is suggested?

This plugin is confused because .lando.yml files may contain a top-level key services:. It says "Missing argument", when in fact all is fine.

These files are not meant for Symfony at all. For example, in the Drupal 8 ecosystem, both Lando and Symfony can coexist without any problems.

For documentation, see https://docs.devwithlando.io.

Example:
I have a project that contains 3 sections - frontend, admin, api
Controllers and related code are placed in separate subfolders inside app folder:
frontend: \App\Http\Controllers
admin: \App\Admin\Http\Controllers
api: \App\Api\Http\Controllers
In my routes I declare this paths via 'namespace' and use short declaration of actions like 'DataController@action'.
What I would like to

What steps will reproduce the problem?

Use this configuration for the queue component:

        'queue' => [
            'class' => \yii\queue\sync\Queue::class,
            'db' => new \yii\helpers\UnsetArrayValue(),
            'tableName' => new \yii\helpers\UnsetArrayValue(),
            'channel' => new \yii\helpers\UnsetArrayValue(),
            'mutex' => new \yii\helpers

/**
 * @ORM\Entity(repositoryClass=TrackerStatusRepository::class)
 */
class TrackerStatus
{
}

1. Alt+Enter on TrackerStatus always has add repository QF if class is specified with constant
2. Find Usages of TrackerStatusRepository shows that class is never used

Parameter "index" doesn't work for Twig functions:

{
    "registrar": [
        {
            "provider": "twig.round_methods",
            "language": "twig",
            "signatures": [
                {
                    "function": "round",
                    "index": 1
                }
            ]
        }
    ],
    "providers": [
        {
            "name": "twig.round_me

Currently a duplicate id in a locallang file will not generate a warning which would be a nice feature

			<trans-unit id="pages.palettes.shortcut">
				<source>Shortcut</source>
			</trans-unit>
			<trans-unit id="pages.palettes.shortcut">
				<source>Shortcut</source>
			</trans-unit>

Since PhpStorm 2019.1 ini vars are bundled with expectedArguments completion.

This results in duplicate entries:

We can remove them now in this plugin.

There is a lot of parameters that may be present in themename.info.yml file. It will be useful to have completion for them.

https://www.drupal.org/docs/8/theming-drupal-8/defining-a-theme-with-an-infoyml-file

Docs: https://www.codeigniter.com/user_guide/general/hooks.html

• Editor notification when hooks are disabled in the config.
• Validation of hook entry (is hook point valid? does class exist? does function exist? etc)
• Inspection: multiple calls to the same hook (offer to make array entries multi-dimensional)