Default implementation expects the value class to reside in the same namespace as its
FieldType class and is named "Value".
-
Example implementation:
-
-protected function checkValueType($value): void
-{
-if ( !$inputValue instanceof \My\FieldType\CookieJar\Value ) )
-{
-throw new InvalidArgumentException( "Given value type is not supported." );
-}
-}
-
+
Example implementation:
+
protected function checkValueType($value): void
+ {
+ if (!$inputValue instanceof \My\FieldType\CookieJar\Value))
+ {
+ throw new InvalidArgumentException("Given value type isn't supported.");
+ }
+ }
+
Returning ACCESS_ABSTAIN must mean that evaluate does not support the provided $object or $targets,
+this is only supported by role limitations as policy limitations should not allow this.
+
Note: In future version constant values might change to 1, 0 and -1 as used in Symfony.
Note: In future version constant values might change to 1, 0 and -1 as used in Symfony.
+
+
@@ -38405,11 +38419,11 @@
Type.php
:
- 33
+ 32
-
Constants for return value of {@see evaluate()}.
+
Access is granted.
@@ -38430,8 +38444,7 @@
-
Currently ACCESS_ABSTAIN must mean that evaluate does not support the provided $object or $targets,
-this is currently only supported by role limitations as policy limitations should not allow this.
Note: In future version constant values might change to 1, 0 and -1 as used in Symfony.
@@ -38443,11 +38456,11 @@
Type.php
:
- 43
+ 66
-
Constants for valueSchema() return values.
+
Limitation's value must be an array of location IDs.
@@ -38468,8 +38481,8 @@
-
Used in cases where a certain value is accepted but the options are to many to return as a hash of options.
-GUI should typically present option to browse content tree to select limitation value(s).
GUI should typically present option to browse content tree to select limitation value(s).
+
+
@@ -38517,7 +38536,7 @@
Type.php
:
- 55
+ 86
@@ -38601,7 +38620,7 @@
Type.php
:
- 78
+ 109
@@ -38618,7 +38637,7 @@
-
public buildValue(array<string|int, mixed> $limitationValues) : Limitation
+
public buildValue(array<int, mixed> $limitationValues) : Limitation
@@ -38628,7 +38647,7 @@
-
The is the method to create values as Limitation type needs value knowledge anyway in acceptValue,
+
This is the method to create values as Limitation type needs value knowledge anyway in acceptValue,
the reverse relation is provided by means of identifier lookup (Value has identifier, and so does RoleService).
Capability flag for custom fields feature for use with {@see ::supports()}.
+
Capability flag for custom fields feature.
@@ -38443,10 +38448,14 @@
-
Custom fields is the capability for search engines to 1. allow you to extend the search index via plugins to
-generate custom fields, like a different representation (format, ...) of an existing field or similar. And 2.
-allow you on some search criteria to specify this custom field to rather query on that instead of the default
-field generated by the system.
Custom fields is the capability for search engines to:
+
+
Allow you to extend the search index via plugins to
+generate custom fields, like a different representation (format, ...) of an existing field or similar.
+
Allow you on some search criteria to specify this custom field to rather query on that instead of the default
+field generated by the system.
+
@@ -38457,11 +38466,11 @@
SearchService.php
:
- 45
+ 49
-
Capability flag for facets feature for use with {@see ::supports()}.
Scoring, a search feature telling you how well one search hit scores compared to other items in the search result.
When this is supported you can expect search engine to populate SearchHit->score and SearchResult->maxScore
properties as well as sort by this if no sort clauses are specified.
@@ -38537,11 +38548,11 @@
SearchService.php
:
- 70
+ 79
-
Capability flag for spellcheck feature for use with {@see ::supports()}.
+
Capability flag for spellcheck feature.
@@ -38562,7 +38573,8 @@
-
Spell check within search capabilities refers to ability to suggest better wordings in fulltext search string.
Spell check within search capabilities refers to ability to suggest better wordings in fulltext search string.
WARNING: This feature is considered experimental given it is not completely designed yet in terms of how it should
interact with FullText criterion (singular) which is the most relevant here. Also given how FullText can be part of a more complex criteria it
might imply a need to more strictly define where users are supposed to place FullText vs other criteria.
@@ -38576,11 +38588,11 @@
SearchService.php
:
- 98
+ 111
-
Capability flag for suggest feature for use with {@see ::supports()}.
+
Capability flag for suggest feature.
@@ -38601,7 +38613,8 @@
-
WARNING: This feature is considered experimental given it is not completely clear what it is supposed to do. Feature
+
WARNING: This feature is considered experimental given it is not completely clear what it is supposed to do. Feature
might be deprecated in the future.
Configuration for specifying prioritized languages query will be performed on.
Also used to define which field languages are loaded for the returned content.
-Currently supports: array("languages" => array(,..), "useAlwaysAvailable" => bool)
-useAlwaysAvailable defaults to true to avoid exceptions on missing translations
Configuration for specifying prioritized languages query will be performed on.
-Currently supports: array("languages" => array(,..), "useAlwaysAvailable" => bool)
-useAlwaysAvailable defaults to true to avoid exceptions on missing translations
Configuration for specifying prioritized languages query will be performed on.
-Currently supports: array("languages" => array(,..), "useAlwaysAvailable" => bool)
-useAlwaysAvailable defaults to true to avoid exceptions on missing translations
+Also used to define which field languages are loaded for the returned content.
+Currently, supports two syntaxeses:
+
Configuration for specifying prioritized languages query will be performed on.
-Currently supports: array("languages" => array(,..), "useAlwaysAvailable" => bool)
-useAlwaysAvailable defaults to true to avoid exceptions on missing translations
@deprecated 4.6.7 accessing magic getter is deprecated and will be removed in 5.0.0. Use Location::getPathString() instead.
+
Accessing magic getter is deprecated since 4.6.7 and will be removed in 5.0.0. Use Location::getPathString() instead.
@@ -39566,7 +39567,7 @@
-
The materialized path of the location entry, eg: /1/2/.
+
The materialized path of the location entry, eg: /1/2/4/23/.
@@ -39695,7 +39696,7 @@
-
a global unique id of the content object
+
A global unique ID of the content object
@@ -39784,7 +39785,7 @@
Location.php
:
- 182
+ 185
@@ -39859,7 +39860,7 @@
Location.php
:
- 191
+ 194
@@ -39902,7 +39903,7 @@
-
the status of the location.
+
The status of the location.
@@ -39923,8 +39924,8 @@
-
a location gets the status DRAFT on newly created content which is not published. When content is published the
-location gets the status STATUS_PUBLISHED
Supported Operators:
-EQ, IN: matches content whose date is or belongs to a list of timestamps
-GT, GTE: matches content whose date is greater than/greater than or equals the given timestamp
-LT, LTE: matches content whose date is lower than/lower than or equals the given timestamp
-BETWEEN: matches content whose date is between (included) the TWO given timestamps
// IN and EQ are supported
return [
// The EQ operator expects a single value, either as an integer or a string
new Specifications(
@@ -38854,11 +38866,11 @@
// IN and EQ are supported
return [
// The EQ operator expects a single value, either as an integer or a string
new Specifications(
@@ -38793,11 +38798,11 @@
// IN and EQ are supported
return [
// The EQ operator expects a single value, either as an integer or a string
new Specifications(
@@ -38683,11 +38690,11 @@
Supports readonly properties by marking them as protected.
+
Supports read-only properties by marking them as protected.
In this case they will only be writable using constructor, and need to be documented
-using property-read <$var> annotation in class doc in addition to inline property doc.
+using @property-read <type> <$var> annotation in class doc in addition to inline property doc.
Writable properties must be public and must be documented inline.
@@ -38370,7 +38370,7 @@
-
public __construct([array<string|int, mixed> $properties = [] ])
+
public __construct([array<string, mixed> $properties = [] ])
@@ -38380,7 +38380,7 @@
-
Readonly properties values must be set using $properties as they are not writable anymore
+
Readonly properties values must be set using $properties as they aren't writable anymore
after object has been created.
@@ -38324,10 +38323,14 @@ 
__isset()
@@ -40104,7 +40123,7 @@