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

• Other Settings
  • Save Actions
    • Activation: activate, file filter, epf (if java)
    • Global Actions: global, build (if compile), execute
    • Java Actions: java fixes

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

Our wp-cli container's home page says 1.2.1 is the latest yet the tags show 1.5.1. This is not good for us if someone only looks at the main page and not the tags page.

Either we need to move to a fully-automated generation of these Docker main pages **or probably better since we can implement sooner we should remove the _"Supported tags and resp

/**
 * @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

@lahmatiy I encountered a bug that open-in-editor does't work correctly when editor is emacs.

Background
reference:
aws-amplify/amplify-cli#1246

Bug summary
When aws-amplify/amplify-cli apply an option of add api, an error occurred as below.

Error: Command failed: osascript -e 'tell application "Terminal" to do script "cd /Users/chris/Projects/t

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