drupal-graphql / drupal-graphql/graphql

TaxonomyLoadTree - cache not invalidated when adding new terms

Open
#1,310 0 comments 0 reactions 0 assignees View on GitHub
4.x
Dominant language
PHP
Stars
287
Forks
198
PR merge metrics
No merged PRs in 30d

Description

When using `taxonomy_load_tree` the resulting cache contains `taxonomy_term:` for each matching term. This doesn't make sense since this producer ~~never accepts any ID arguments~~, meaning the cache will be stale unless you edit an entity in the original result set.

Since 8.x-support has been dropped, couldn't this producer result simply be cached by `_list:` without any major impact?

EDIT:
Case of the mondays, it's possible to pass a specific term ID (parent). But I don't think it changes much in context of cacheability - if I add a new term underneath a parent, unless it forces clears of already existing terms, it's still the same situation.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.