- Issue created by @DamienMo
- Merge request !6940Draft: add filters_to_skip capabillity to preRenderText to skip filters processing on fields. → (Open) created by DamienMo
- 🇺🇸United States smustgrave
Since we don't have a filter sub-maintainer going to need framework manager sign off if this is a feature they would accept.
If so then will need test coverage.
- Status changed to Needs work
about 1 year ago 12:22am 11 March 2024 - 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
I'm not in favour of this change, it could lead to quirky cache bugs.
The output of filters is cached, and in the current code-path there is no consideration of cache keys based on filters to skip.
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Any reason you can't use a different input format in a different formatter which has different filters? Feels like that can be achieved as is.
- 🇨🇭Switzerland DamienMo
Any reason you can't use a different input format in a different formatter which has different filters? Feels like that can be achieved as is.
I'm not sure what you mean. I see no way I can change input formatter for different node view modes.
I'm not familiar with how to add cache tags for the filters to skip can someone help here ?
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
So you can create a formatter, and it can return a render array of type processed_text and set a different format.
That's the idea I'm suggesting
- 🇨🇭Switzerland DamienMo
When I use the formatter on a node field, the same formatter is used in every node view mode. I can't change input formatter depending on node view modes like you are suggesting.
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
If you write a custom formatter you can, that's what I'm proposing
- Status changed to Closed: works as designed
3 months ago 12:15pm 30 November 2024 - 🇳🇿New Zealand quietone
Reading the comments this is a Support Request and further, it has been answered by @larowlan,