When rendering the inner fields, it doesn't propagate the relevant cache tags up.
This is more relevant when used with the views_field_view → which can be used to include custom views which contain their own cache tags, which should cause the parent view cache to be invalidated when something within the child view is changed.
Create a view with field (e.g. views_field_view) which has a special cache tag attached to it, this special cache tag will not be included in the final response.
This is because the cache data is attached to the current RenderContext, but later lost since it's not applied back to the final render array.
Pop and apply any of the relevant render context back to the final view.
Provide issue fork/patch
N/A
Active
1.0
Code
This looks right to me, I'm not sure how to write a test for it.
Any ideas without adding a dev dependency for views_field_views?