Needs work
Project:
Drupal core
Version:
main
Component:
theme system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Jul 2020 at 13:58 UTC
Updated:
8 Apr 2023 at 23:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
sarvjeetsingh commentedAs the referenced issue is closed and the function
theme_render_and_autoescapeis not deprecated. I think we can remove this todo docblock.uploaded a patch for the same.
Comment #3
ranjith_kumar_k_u commentedI have reviewed the above patch ,it removes closed issue reference @todo comment from theme_render_and_autoescape function.RTBC
Comment #4
ranjith_kumar_k_u commentedComment #6
anmolgoyal74 commentedRemoved the message from one more file as well.
Comment #8
tanubansal commentedTested #6, this can be moved to RTBC
Comment #9
richardbporter commentedI'm still unclear on this one. Yes the referenced issue was closed but was deprecating `theme_render_and_autoescape` ever discussed?
Also, I'm not sure this was addressed.
Maybe it should point to the deprecation policy? https://www.drupal.org/node/2856615
Comment #12
vikashsoni commented#6 patch applied successfully
After patch @todo comment has been removed
Thanks for the patch
Comment #14
vighneshh commented#6 patch applied moving issue to RTBC.
Comment #15
catchWe should update the @todo in theme_render_and_autoescape() to point to a new issue for deprecating and removing it - it's only used in test coverage and core no longer supports theme functions.
The query hunk looks unrelated to the title here, and should also point to a new issue for triggering a deprecation error when term_access is passed.
Comment #16
rakhi soni commentedKindly review patch for version 9.5x,,
Comment #17
vinmayiswamy commented#16 patch applied successfully in Drupal 9.5.x-dev
Thanks @Rakhi Soni
Comment #18
longwaveAs per #15 we can't just remove either of these comments.
Re deprecating
theme_render_and_autoescape()the question is whether we should keep this in core for other (hypothetical?) theme engines to use, or whether we should leave escaping to be implemented by theme engine itself. If we do decide to deprecate and remove it we can also close #2575065: Refactor theme_escape_and_render() and TwigExtension::escapeFilter() to share reused code.The term_access comment should be updated to point to #3261261: Properly deprecate term_access query tag
Comment #19
longwaveI searched contrib and can find no valid uses of
theme_render_and_autoescape()so I think it should be deprecated and removed.Comment #20
longwaveOpened #3299946: Deprecate theme_render_and_autoescape()
So to summarise:
theme_render_and_autoescape() can point to #3299946: Deprecate theme_render_and_autoescape()
term_access can point to #3261261: Properly deprecate term_access query tag
Comment #21
bnjmnmPatch #6 still applies to 9.5, so there was no reason for the reroll in #16 ant it is the same as the patch aa #6, so I'm preemptively removing credit.
Also, #16 shouldn't have had its status set to "needs review". It was set to "needs work" prior to that because specific changes were requested. It shouldn't be switched to "needs review" until those changes are implemented. Even if it were a necessary reroll, rerolls by themselves do not require review.
Comment #22
bnjmnmComment #24
smustgrave commentedMoving to NW For #20
Comment #25
smustgrave commented@longwave like this? I couldn't find an example of inline deprecation
Comment #26
longwaveThis issue exists just to update the @todos. But instead of just repointing them, I added patches for both @todos instead:
#3299946: Deprecate theme_render_and_autoescape()
#3261261: Properly deprecate term_access query tag
Comment #27
smustgrave commentedShould this be closed then?