Adds the configuration level to the component hierarchy, through which the data API can be extended into an application
Via Composer
composer require getpop/component-model-configurationThe source code is hosted on the GatoGraphQL monorepo, under SiteBuilder/packages/component-model-configuration.
Initialize the component:
\PoP\Root\App::stockAndInitializeModuleClasses([([
\PoP\ConfigurationComponentModel\Module::class,
]);Configuration values are added under functions:
function getImmutableConfiguration($component, &$props)function getMutableonmodelConfiguration($component, &$props)function getMutableonrequestConfiguration($component, &$props)
For instance:
// Implement the components properties ...
function getImmutableConfiguration($component, &$props)
{
$ret = parent::getImmutableConfiguration($component, $props);
switch ($component->name) {
case self::COMPONENT_SOMENAME:
$ret['description'] = __('Some description');
$ret['classes']['description'] = 'jumbotron';
break;
}
return $ret;
}Please notice that the configuration receives the $props parameter, hence it can print configuration values set through props. immutable and mutable on model configuration values are initialized through initModelProps, and mutable on request ones are initialized through initRequestProps:
// Implement the components properties ...
function getImmutableConfiguration($component, &$props)
{
$ret = parent::getImmutableConfiguration($component, $props);
switch ($component->name) {
case self::COMPONENT_SOMENAME:
$ret['showmore'] = $this->getProp($component, $props, 'showmore');
$ret['class'] = $this->getProp($component, $props, 'class');
break;
}
return $ret;
}
function initModelProps($component, &$props)
{
switch ($component->name) {
case self::COMPONENT_SOMENAME:
$this->setProp($component, $props, 'showmore', false);
$this->appendProp($component, $props, 'class', 'text-center');
break;
}
parent::initModelProps($component, $props);
}To cache the configuration for all components in the client, and keep them available to be reused, we simply deep merge all the responses together. For instance, if the first request brings this response:
{
"component1": {
configuration: {
class: "topcomponent"
},
components: {
"component2": {
configuration: {
class: "some-class"
}
}
}
}
}And the second response brings this response:
{
"component3": {
configuration: {
class: "topcomponent"
},
components: {
"component4": {
configuration: {
class: "another-class"
}
}
}
}
}Then deep merging the responses together will result in:
{
"component1": {
configuration: {
class: "topcomponent"
},
components: {
"component2": {
configuration: {
class: "some-class"
}
}
}
},
"component3": {
configuration: {
class: "topcomponent"
},
components: {
"component4": {
configuration: {
class: "another-class"
}
}
}
}
}And we can perfectly reuse the configuration starting from "component1" to reprint the first request, and the configuration starting from "component3" to reprint the second request.
That was easy, however from now on it gets more complicated. What happens if the component's descendants are not static, but can change depending on the context, such as the requested URL or other inputs? For instance, we could have a component "single-post" which changes its descendant component based on the post type of the requested object, choosing between components "layout-post" or "layout-event", so that the component hierarchy alternates from this:
"single-post"
components
"layout-post"to this:
"single-post"
components
"layout-event"Similarly, even within the same component hierarchy, a component could have a property value change for different URLs. For instance, a component "post-layout" can have a property "class" with value "post-{id}", where "{id}" is the id of the requested post, so that we can add styles for specific posts such as .post-37 { background-color: red; } and .post-224 { background-color: green; }. Then, posts with ids 37 and 224, even though they have the same component hierarchy, their configurations will alternate from this:
"single-post"
components
"layout-post"
configuration
class: "post-37"to this:
"single-post"
components
"layout-post"
configuration
class: "post-224"Let's explore what happens in these two situations described above when deep merging the results. In the first case, for instance, if the first request brings this response:
{
"component1": {
configuration: {
class: "topcomponent"
},
components: {
"component2": {
configuration: {
class: "some-class"
}
}
}
}
}And the second response brings this response:
{
"component1": {
configuration: {
class: "topcomponent"
},
components: {
"component3": {
configuration: {
class: "another-class"
}
}
}
}
}Then deep merging the responses together will result in:
{
"component1": {
configuration: {
class: "topcomponent"
},
components: {
"component2": {
configuration: {
class: "some-class"
}
},
"component3": {
configuration: {
class: "another-class"
}
}
}
}
}As it can be seen, after merging the response from the second request, the data that was the same (class: "topcomponent") didn't affect the merged object, and the new information was appended to the existing object but without overriding any data. However, originally the first response has "component1" with only "component2" as a descendant, but after the merge, "component1" has two descendants, "component2" and "component3". Then, if loading again the URL for the first response and reusing the cached configuration, below "component1" it will print "component2" and "component3" instead of only "component2" as it should be.
To address this issue, the configuration can add a property "descendants" explicitly declaring which are its subcomponents, to know which components must be rendered and ignore the rest, even though their data is still part of the merged JSON object. Then, the first and second response will look like this:
{
"component1": {
configuration: {
class: "topcomponent",
descendants: ["component2"]
},
components: {
"component2": {
configuration: {
class: "some-class"
}
}
}
}
}
{
"component1": {
configuration: {
class: "topcomponent",
descendants: ["component3"]
},
components: {
"component3": {
configuration: {
class: "another-class"
}
}
}
}
}And the merged configuration will look like this:
{
"component1": {
configuration: {
class: "topcomponent",
descendants: ["component3"]
},
components: {
"component2": {
configuration: {
class: "some-class"
}
},
"component3": {
configuration: {
class: "another-class"
}
}
}
}
}But now, the value for property "descendants" in the cached object has been overriden with the value from the second response, bringing us to the second issue stated earlier on about differing property values. Then, if loading again the URL for the first response and reusing the cached configuration, below "component1" it will print "component3" instead of "component2" as it should be.
The issue about differing properties arises from the fact that configuration values are set not only according to the component hierarchy, but also to the requested URL. For instance, the following component hierarchy:
"single-post"
components
"layout-post"Can produce the following two different configuration outputs:
"single-post"
components
"layout-post"
configuration
class: "post-37"and
"single-post"
components
"layout-post"
configuration
class: "post-224"The solution is to deep merge the configurations from different requests without overriding differing properties, either at the component hierarchy or URL levels, is to have the configuration split into 3 separate subsections: "immutable", "mutableonmodel" (where "model" is equivalent to "component hierarchy") and "mutableonrequest". Every property in the configuration must be placed under exactly 1 of the 3 sections, like this:
- immutable: Contains properties which never change, such as
class: "topcomponent" - mutableonmodel: Contains properties which can change based on the component hierarchy, such as
descendants: ["component2"] - mutableonrequest: Contains properties which can change based on the requested URL, such as
class: "post-37"
Following this scheme, a first request may produce the following response:
{
immutable: {
"single-post": {
configuration: {
class: "topcomponent"
}
}
},
mutableonmodel: {
"single-post": {
configuration: {
descendants: ["layout-post"]
}
}
},
mutableonrequest: {
"single-post": {
components: {
"layout-post": {
configuration: {
class: "post-37"
}
}
}
}
}
}As it can be observed, because the properties from the 3 sections do not overlap, then merging the 3 sections for the request produces the whole configuration once again:
{
"single-post": {
configuration: {
class: "topcomponent",
descendants: ["layout-post"]
},
components: {
"layout-post": {
configuration: {
class: "post-37"
}
}
}
}
}Next, the cache in the client is kept in 3 separate objects, one for each of the subsections, with sections "mutableonmodel" and "mutableonrequest" storing their data under appropriate keys: "mutableonmodel" under a key called "modelInstanceId", which represents a hash of the component hierarchy, and "mutableonrequest" under the requested URL. The request above will then be cached like this (assuming a "modelInstanceId" with value "bwKtq*8H" and URL "/posts/some-post/"):
immutable =>
{
"single-post": {
configuration: {
class: "topcomponent"
}
}
}
mutableonmodel =>
{
"bwKtq*8H": {
"single-post": {
configuration: {
descendants: ["layout-post"]
}
}
}
}
mutableonrequest =>
{
"/posts/some-post/": {
"single-post": {
components: {
"layout-post": {
configuration: {
class: "post-37"
}
}
}
}
}
}If then we obtain the response for a second request, the cache is updated like this (assuming a "modelInstanceId" with value "6C7Lu$\3" and URL "/posts/some-event/"):
immutable =>
{
"single-post": {
configuration: {
class: "topcomponent"
}
}
}
mutableonmodel =>
{
"bwKtq*8H": {
"single-post": {
configuration: {
descendants: ["layout-post"]
}
}
},
"6C7Lu$\3": {
"single-post": {
configuration: {
descendants: ["layout-event"]
}
}
}
}
mutableonrequest =>
{
"/posts/some-post/": {
"single-post": {
components: {
"layout-post": {
configuration: {
class: "post-37"
}
}
}
}
},
"/posts/some-event/": {
"single-post": {
components: {
"layout-event": {
configuration: {
class: "post-45"
}
}
}
}
}
}As it can be observed, "immutable" holds the common parts of the structure, while "mutableonmodel" and "mutableonrequest" hold the deltas. Hence, this scheme identifies common data and stores it only once, and all dissimilar entries are stored and accessible on their own. If most of the configuration doesn't change within the component hierarchy, then the information stored under "immutable" will make the bulk of the stored information, succeeding in minimizing the amount of data that is cached.
Finally, given the "modelInstanceId" and URL for any request we can obtain the 3 separate branches from the 3 sections, and merge them all together to recreate the whole configuration from the cache.
The merging can be done in the server-side too: If there is no need to cache the configuration on the client, then we can avoid the added complexity of dealing with the three subsections by adding parameter dataoutputmode=combined to the URL.
Requirements:
- PHP 8.1+ for development
- PHP 7.2+ for production
Check the list of Supported PHP features in GatoGraphQL/GatoGraphQL
Via Rector (dry-run mode):
composer preview-code-downgradeTo check the coding standards via PHP CodeSniffer, run:
composer check-styleTo automatically fix issues, run:
composer fix-stylePlease see CHANGELOG for more information on what has changed recently.
To execute PHPUnit, run:
composer testTo execute PHPStan, run:
composer analyseTo report a bug or request a new feature please do it on the GatoGraphQL monorepo issue tracker.
We welcome contributions for this package on the GatoGraphQL monorepo (where the source code for this package is hosted).
Please see CONTRIBUTING and CODE_OF_CONDUCT for details.
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
GNU General Public License v2 (or later). Please see License File for more information.