Inline annotations are not recognized

[RolfBabijn]

Inline annotations are not recognised and will give a warning that there is no import for it. When I use the annotation in a docblock for a method or class it will work.

<?php

namespace Gadgetdude\AcmeBundle\Controller;

use Gadgetdude\AcmeBundle\Annotation\Ignore;

/**
 * @Ignore (Is resolved correctly)
 */
class TestController
{
    /**
     * @Ignore (Is resolved correctly)
     */
    public function annotationAction()
    {
        /** @Ignore (Is not resolved, results in warning) */
        return $this->doSomethingPrivate();
    }

    // ...
}

Interesting is that when the annotation is only used inline (which results in a warning) does not result in a unused warning for the use statement above.

<?php

namespace Gadgetdude\AcmeBundle\Controller;

use Gadgetdude\AcmeBundle\Annotation\Ignore; // No unused warning

class TestController
{
    public function annotationAction()
    {
        /** @Ignore (Is not resolved, results in warning) */
        return $this->doSomethingPrivate();
    }

    // ...
}

I've tested it in the last versions of PhpStorm (7.1.3, 7.1.4 and 8.0). The only other custom plugin I have enabled is the Symfony framework plugin, but I don't think that would be an issue (it never was before). The problem I'm having is a recent problem, probably introduced in 1.4 of this plugin or maybe one version earlier?

[domis86]

+1
same problem

[RolfBabijn]

Tested with latest tag release (1.4.1). Problem still exists.

[Haehnchen]

fixed, pls validate

[domis86]

@Haehnchen Problem still exists - but a bit different.

Here the "@desc" annotation doesnt seem to be detected as annotation (cannot ctrl+hover on it etc)
code inspection says: "Alias 'JMSTranslationBundleAnnotationDesc' is never used (at line 5)"

Here full named "@jms\TranslationBundle\Annotation\Desc" annotation is recognized correctly:

[RolfBabijn]

Confirming problem in version 1.5.1 as reported by @domis86.

[RolfBabijn]

Any updates yet @Haehnchen?

[Haehnchen]

this is a single use case of JMSTranslationBundle. i didnt found other similar projects, so in my opinion it should not implement here, as long as we not have the arguments.

[RolfBabijn]

Sad to hear that, but I can't imagine that JMSTranslationBundle is the only library out there that is using annotations in inline docblocks. I also wonder why this did work in previous versions of the PHP Annotation plugin.

[mrgix]

Same problem here. Please fix.

[MvanRietschoten]

+1 It's a correct doc block, why shouldn't it work?

[Haehnchen]

instead scanning for annotations before class, functions and properties definition only, i need to walk through the complete file for fully support this use case. pls, just deliver some other projects and i will rethink this behavior. i cant reduce overall performance just for one use case.

[cyberwolf]

I just installed this plugin, as I wanted it to assist me while documenting my RESTfull API built in Silex. Unfortunately I also stumbled on the fact that annotations are only autocompleted when used in front of classes, functions and properties, while what I need to document are Silex routes. So +1 from me to widen the scope of where these annotations can be autocompleted.