- Issue created by @mkalkbrenner
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Seems reasonable - is there a way we can add a test for this bug?
- 🇮🇳India rakesh.regar Rajasthan, India
rakesh.regar → made their first commit to this issue’s fork.
The hal module permanently caches relation IDs.
If that cache gets build via LinkManager::getRelationInternalIds(), broken data could be cached.
The problem is that LinkManager::getRelationInternalIds() doesn't forward the context to RelationLinkManager::getRelationInternalIds().
This breaks two functionalities:
hook_hal_relation_uri_alter() gets an empty context which might lead to different resultsCacheableNormalizerInterface::SERIALIZATION_CONTEXT_CACHEABILITY context gets lost. So, LinkManagerBase::getLinkDomain() can not add the configs hal.settings or url.site. This causes illegal values returned by cache later if these configs changeThis is an critical issue because it leads to broken JSON files. Or in case of the default_content_deploy module, the denormalization of references fails.
Active
2.0
Code
Seems reasonable - is there a way we can add a test for this bug?
rakesh.regar → made their first commit to this issue’s fork.