You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a UseImportOption maps a concrete class to an alias, the plugin should autocomplete on it.
Example:
ClassName is TYPO3\CMS\Extbase\Annotation\Inject, alias is inject. What we need, is completion for lowercase @inject. I know this seems a bit clunky since we can alias an annotation to almost anything, but TYPO3 CMS recently introduced doctrine annotations and to minimize the impact, the current best-practice is to alias the new Inject Annotation to the old @inject phpDoc tag.
Currently, the completion provider completes the Annotation since there's nothing special, but when selected, it imports the annotation as specified (use TYPO3\CMS\Extbase\Annotation\Inject as inject) then inserts @Inject (which is not the correct value in this case) and then, to make it even worse, imports the Inject class once again. Sigh.
The text was updated successfully, but these errors were encountered:
When a UseImportOption maps a concrete class to an alias, the plugin should autocomplete on it.
Example:
ClassName is
TYPO3\CMS\Extbase\Annotation\Inject
, alias isinject
. What we need, is completion for lowercase@inject
. I know this seems a bit clunky since we can alias an annotation to almost anything, but TYPO3 CMS recently introduced doctrine annotations and to minimize the impact, the current best-practice is to alias the newInject
Annotation to the old@inject
phpDoc tag.Currently, the completion provider completes the Annotation since there's nothing special, but when selected, it imports the annotation as specified (
use TYPO3\CMS\Extbase\Annotation\Inject as inject
) then inserts@Inject
(which is not the correct value in this case) and then, to make it even worse, imports theInject
class once again. Sigh.The text was updated successfully, but these errors were encountered: