Problem/Motivation

Core now has a built-in render cache debug output https://www.drupal.org/node/3162480.

Proposed resolution

Should we deprecate this module or make a new version based on this output?

Comments

Grimreaper created an issue. See original summary.

anybody’s picture

Well comparing both I still think this module is very helpful as it - as the module name says - visualizes the results, while the core
renderer.config.debug: true simply adds HTML comments.

So I'd vote to keep this! :)

dpi’s picture

Could we at least link https://www.drupal.org/node/3162480 and https://www.drupal.org/project/cache_review from the project page in the meantime?

fgm’s picture

Confirmed this is much more convenient than comments in markup as comments are mostly useful to check what exists around a given element, while Renderviz allows discovering all that exists in a page, to pinpoint what is bringing a specific tag, context, or max-age.

grimreaper’s picture

Hi,

@dpi, links added to the project page.

So we need to determine if it would be possible to use Core render cache output and only keep the JS for visualization?

That way we will avoid the bug from #2847712: Broken markup

grimreaper’s picture

Then should the module be reworked to use Core cache debug output and only focus on visualization or the data exposed by the module are more precised than core ones?

grimreaper’s picture

Status: Active » Closed (won't fix)

Thanks for your feedbacks. Closing as won't fix.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.