Created
May 8, 2014 15:55
-
-
Save emodric/2c888f45c265873866a2 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eddie@abyss: ~/repos/netgen/TagsBundle/vendor/ezsystems/ezpublish-kernel [master] $ grep -irn "criterions" * | |
eZ/Publish/SPI/Persistence/Content/Search/Handler.php:42: * @throws \eZ\Publish\API\Repository\Exceptions\InvalidArgumentException if there is more than than one result matching the criterions | |
eZ/Publish/API/Repository/SearchService.php:45: * @throws \eZ\Publish\API\Repository\Exceptions\InvalidArgumentException if there is more than than one result matching the criterions | |
eZ/Publish/API/Repository/Values/Content/Search/SearchResult.php:35: * criterions the wrong spelled value is replaced by a corrected one (TBD). | |
eZ/Publish/API/Repository/Values/Content/Query/Criterion.php:43: * Additional value data, required by some criterions, MapLocationDistance for instance | |
eZ/Publish/API/Repository/Values/Content/Query/Criterion/Location.php:18: * This is the base class for Location criterions | |
eZ/Publish/Core/Repository/SearchService.php:147: * Checks that $criteria does not contain Location criterions. | |
eZ/Publish/Core/Repository/SearchService.php:161: $argumentName, "Location criterions cannot be used in Content search" | |
eZ/Publish/Core/Repository/SearchService.php:242: * @throws \eZ\Publish\API\Repository\Exceptions\InvalidArgumentException if there is more than one result matching the criterions | |
eZ/Publish/Core/Repository/LocationService.php:28:use eZ\Publish\API\Repository\Values\Content\Query\Criterion\Subtree as CriterionSubtree; | |
eZ/Publish/Core/Repository/LocationService.php:147: new CriterionSubtree( $loadedSubtree->pathString ), | |
eZ/Publish/Core/Repository/LocationService.php:657: new CriterionSubtree( $location->pathString ), | |
eZ/Publish/Core/Repository/LocationService.php:742: new CriterionSubtree( $location->pathString ), | |
eZ/Publish/Core/Repository/Tests/Service/Mock/SearchTest.php:99: "Argument '\$query' is invalid: Location criterions cannot be used in Content search" | |
eZ/Publish/Core/Repository/Tests/Service/Mock/SearchTest.php:103: "Argument '\$query' is invalid: Location criterions cannot be used in Content search" | |
eZ/Publish/Core/Repository/Tests/Service/Mock/SearchTest.php:115: "Argument '\$query' is invalid: Location criterions cannot be used in Content search" | |
eZ/Publish/Core/Repository/Tests/Service/Mock/SearchTest.php:164: "Argument '\$filter' is invalid: Location criterions cannot be used in Content search" | |
eZ/Publish/Core/Repository/Tests/Service/Mock/SearchTest.php:172: "Argument '\$filter' is invalid: Location criterions cannot be used in Content search" | |
eZ/Publish/Core/SignalSlot/SearchService.php:76: * @throws \eZ\Publish\API\Repository\Exceptions\InvalidArgumentException if there is more than than one result matching the criterions | |
eZ/Publish/Core/Persistence/Solr/Content/Search/Handler.php:152: * @throws \eZ\Publish\API\Repository\Exceptions\InvalidArgumentException if there is more than than one result matching the criterions | |
eZ/Publish/Core/Persistence/Legacy/Content/Search/Handler.php:133: * @throws \eZ\Publish\API\Repository\Exceptions\InvalidArgumentException if there is more than than one result matching the criterions | |
eZ/Publish/Core/Limitation/Tests/ContentTypeLimitationTypeTest.php:426: public function testGetCriterionSingleValue( ContentTypeLimitationType $limitationType ) | |
eZ/Publish/Core/Limitation/Tests/LocationLimitationTypeTest.php:508: public function testGetCriterionSingleValue( LocationLimitationType $limitationType ) | |
eZ/Publish/Core/Limitation/Tests/SubtreeLimitationTypeTest.php:567: public function testGetCriterionSingleValue( SubtreeLimitationType $limitationType ) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment