Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It makes sense to rename the ViewsDataCache class to just ViewsData, it manages the views data, and just happens to use the cache backend and manage the getting/setting. So it's not just a cache it IS views data objectified :)
Also based on #1962234: [Change notice] Move views_fetch_fields into an autoloadable class I think that issue should use a class ViewsDataHelper.
Comment | File | Size | Author |
---|---|---|---|
#4 | 1989806-4.patch | 14.11 KB | damiankloip |
vdc.ViewsDataCache-rename.patch | 13.06 KB | damiankloip | |
Comments
Comment #2
damiankloip CreditAttribution: damiankloip commentedvdc.ViewsDataCache-rename.patch queued for re-testing.
Comment #4
damiankloip CreditAttribution: damiankloip commentedSorry, didn't include the actual changes to ViewsDataCache in the patch!!!
Comment #5
dawehnerJust to be sure similar systems in core are named the following: ThemeRegistry, SchemaCache, ModuleInfo, AliasWhitelist. To sum it up, it would be more consistent to rename it.
Yeah, this always confused me.
Comment #6
damiankloip CreditAttribution: damiankloip commented#4: 1989806-4.patch queued for re-testing.
Comment #7
catchCommitted/pushed to 8.x, thanks!
Comment #8.0
(not verified) CreditAttribution: commentedUpdated issue summary.