TYPO3 /
typo3
| 1 | <?php |
||||||||||
| 2 | |||||||||||
| 3 | /** |
||||||||||
| 4 | * Extend PhpStorms code completion capabilities by providing a meta file |
||||||||||
| 5 | * |
||||||||||
| 6 | * Kudos to Alexander Schnitzler's work, see https://github.com/alexanderschnitzler/phpstorm.meta.php-typo3 |
||||||||||
| 7 | * @link https://www.jetbrains.com/help/phpstorm/ide-advanced-metadata.html |
||||||||||
| 8 | */ |
||||||||||
| 9 | |||||||||||
| 10 | namespace PHPSTORM_META { |
||||||||||
| 11 | // Tests |
||||||||||
| 12 | override(\TYPO3\TestingFramework\Core\BaseTestCase::getAccessibleMock(0), type(0)); |
||||||||||
|
0 ignored issues
–
show
Bug
Best Practice
introduced
by
Loading history...
|
|||||||||||
| 13 | override(\TYPO3\TestingFramework\Core\BaseTestCase::getAccessibleMockForAbstractClass(0), type(0)); |
||||||||||
|
0 ignored issues
–
show
The method
TYPO3\TestingFramework\C...eMockForAbstractClass() is not static, but was called statically.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
|
|||||||||||
| 14 | |||||||||||
| 15 | // Contexts |
||||||||||
| 16 | // @see https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.4/Feature-85389-ContextAPIForConsistentDataHandling.html |
||||||||||
| 17 | expectedArguments( |
||||||||||
| 18 | \TYPO3\CMS\Core\Context\Context::getAspect(), |
||||||||||
|
0 ignored issues
–
show
The method
TYPO3\CMS\Core\Context\Context::getAspect() is not static, but was called statically.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
The call to
TYPO3\CMS\Core\Context\Context::getAspect() has too few arguments starting with name.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check compares calls to functions or methods with their respective definitions. If the call has less arguments than are defined, it raises an issue. If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above. Loading history...
|
|||||||||||
| 19 | 0, |
||||||||||
| 20 | 'date', |
||||||||||
| 21 | 'visibility', |
||||||||||
|
0 ignored issues
–
show
The call to
PHPSTORM_META\expectedArguments() has too many arguments starting with 'visibility'.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue. If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above. Loading history...
|
|||||||||||
| 22 | 'backend.user', |
||||||||||
| 23 | 'frontend.user', |
||||||||||
| 24 | 'workspace', |
||||||||||
| 25 | 'language', |
||||||||||
| 26 | 'typoscript' |
||||||||||
| 27 | ); |
||||||||||
| 28 | |||||||||||
| 29 | override(\TYPO3\CMS\Core\Context\Context::getAspect(), map([ |
||||||||||
|
0 ignored issues
–
show
TYPO3\CMS\Core\Context\Context::getAspect() of type TYPO3\CMS\Core\Context\AspectInterface is incompatible with the type callable expected by parameter $callable of PHPSTORM_META\override().
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
|
|||||||||||
| 30 | 'date' => \TYPO3\CMS\Core\Context\DateTimeAspect::class, |
||||||||||
| 31 | 'visibility' => \TYPO3\CMS\Core\Context\VisibilityAspect::class, |
||||||||||
| 32 | 'backend.user' => \TYPO3\CMS\Core\Context\UserAspect::class, |
||||||||||
| 33 | 'frontend.user' => \TYPO3\CMS\Core\Context\UserAspect::class, |
||||||||||
| 34 | 'workspace' => \TYPO3\CMS\Core\Context\WorkspaceAspect::class, |
||||||||||
| 35 | 'language' => \TYPO3\CMS\Core\Context\LanguageAspect::class, |
||||||||||
| 36 | 'typoscript' => \TYPO3\CMS\Core\Context\TypoScriptAspect::class, |
||||||||||
| 37 | ])); |
||||||||||
| 38 | |||||||||||
| 39 | expectedArguments( |
||||||||||
| 40 | \TYPO3\CMS\Core\Context\DateTimeAspect::get(), |
||||||||||
|
0 ignored issues
–
show
The method
TYPO3\CMS\Core\Context\DateTimeAspect::get() is not static, but was called statically.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
The call to
TYPO3\CMS\Core\Context\DateTimeAspect::get() has too few arguments starting with name.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check compares calls to functions or methods with their respective definitions. If the call has less arguments than are defined, it raises an issue. If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above. Loading history...
|
|||||||||||
| 41 | 0, |
||||||||||
| 42 | 'timestamp', |
||||||||||
| 43 | 'iso', |
||||||||||
| 44 | 'timezone', |
||||||||||
| 45 | 'full', |
||||||||||
| 46 | 'accessTime' |
||||||||||
| 47 | ); |
||||||||||
| 48 | |||||||||||
| 49 | expectedArguments( |
||||||||||
| 50 | \TYPO3\CMS\Core\Context\VisibilityAspect::get(), |
||||||||||
|
0 ignored issues
–
show
The call to
TYPO3\CMS\Core\Context\VisibilityAspect::get() has too few arguments starting with name.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check compares calls to functions or methods with their respective definitions. If the call has less arguments than are defined, it raises an issue. If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above. Loading history...
The method
TYPO3\CMS\Core\Context\VisibilityAspect::get() is not static, but was called statically.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
|
|||||||||||
| 51 | 0, |
||||||||||
| 52 | 'includeHiddenPages', |
||||||||||
| 53 | 'includeHiddenContent', |
||||||||||
| 54 | 'includeDeletedRecords' |
||||||||||
| 55 | ); |
||||||||||
| 56 | |||||||||||
| 57 | expectedArguments( |
||||||||||
| 58 | \TYPO3\CMS\Core\Context\UserAspect::get(), |
||||||||||
|
0 ignored issues
–
show
The method
TYPO3\CMS\Core\Context\UserAspect::get() is not static, but was called statically.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
The call to
TYPO3\CMS\Core\Context\UserAspect::get() has too few arguments starting with name.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check compares calls to functions or methods with their respective definitions. If the call has less arguments than are defined, it raises an issue. If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above. Loading history...
|
|||||||||||
| 59 | 0, |
||||||||||
| 60 | 'id', |
||||||||||
| 61 | 'username', |
||||||||||
| 62 | 'isLoggedIn', |
||||||||||
| 63 | 'isAdmin', |
||||||||||
| 64 | 'groupIds', |
||||||||||
| 65 | 'groupNames' |
||||||||||
| 66 | ); |
||||||||||
| 67 | |||||||||||
| 68 | expectedArguments( |
||||||||||
| 69 | \TYPO3\CMS\Core\Context\WorkspaceAspect::get(), |
||||||||||
|
0 ignored issues
–
show
The method
TYPO3\CMS\Core\Context\WorkspaceAspect::get() is not static, but was called statically.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
The call to
TYPO3\CMS\Core\Context\WorkspaceAspect::get() has too few arguments starting with name.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check compares calls to functions or methods with their respective definitions. If the call has less arguments than are defined, it raises an issue. If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above. Loading history...
|
|||||||||||
| 70 | 0, |
||||||||||
| 71 | 'id', |
||||||||||
| 72 | 'isLive', |
||||||||||
| 73 | 'isOffline' |
||||||||||
| 74 | ); |
||||||||||
| 75 | |||||||||||
| 76 | expectedArguments( |
||||||||||
| 77 | \TYPO3\CMS\Core\Context\LanguageAspect::get(), |
||||||||||
|
0 ignored issues
–
show
The method
TYPO3\CMS\Core\Context\LanguageAspect::get() is not static, but was called statically.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
The call to
TYPO3\CMS\Core\Context\LanguageAspect::get() has too few arguments starting with name.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check compares calls to functions or methods with their respective definitions. If the call has less arguments than are defined, it raises an issue. If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above. Loading history...
|
|||||||||||
| 78 | 0, |
||||||||||
| 79 | 'id', |
||||||||||
| 80 | 'contentId', |
||||||||||
| 81 | 'fallbackChain', |
||||||||||
| 82 | 'overlayType', |
||||||||||
| 83 | 'legacyLanguageMode', |
||||||||||
| 84 | 'legacyOverlayType' |
||||||||||
| 85 | ); |
||||||||||
| 86 | |||||||||||
| 87 | expectedArguments( |
||||||||||
| 88 | \TYPO3\CMS\Core\Context\TypoScriptAspect::get(), |
||||||||||
|
0 ignored issues
–
show
The call to
TYPO3\CMS\Core\Context\TypoScriptAspect::get() has too few arguments starting with name.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check compares calls to functions or methods with their respective definitions. If the call has less arguments than are defined, it raises an issue. If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above. Loading history...
The method
TYPO3\CMS\Core\Context\TypoScriptAspect::get() is not static, but was called statically.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
|
|||||||||||
| 89 | 0, |
||||||||||
| 90 | 'forcedTemplateParsing' |
||||||||||
| 91 | ); |
||||||||||
| 92 | } |
||||||||||
| 93 |