Problem/Motivation
Shortcut module users a database table to store user shortcut sets:
MariaDB [db]> DESCRIBE shortcut_set_users;
+----------+------------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+----------+------------------+------+-----+---------+-------+
| uid | int(10) unsigned | NO | PRI | 0 | |
| set_name | varchar(32) | NO | MUL | | |
+----------+------------------+------+-----+---------+-------+
2 rows in set (0.003 sec)
this means separate database queries to lookup the shortcut set for a user. It could be a base field on users, then it wouldn't require the extra query.
Found via #3437576: Provide a new user.shortcut_set cache context.
Comments
Comment #2
pcambraJust pointing out that this is something I'm working on on https://www.drupal.org/sandbox/pcambra/3421093, specifically https://www.drupal.org/project/3421093/issues/3428572
Comment #3
xjmComment #5
quietone commentedThe Shortcut Module was approved for removal in #3476880: [Policy] Move Shortcut module to contrib.
This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
The deprecation work is in #3569117: [meta] Tasks to deprecate the Shortcut module and the removal work in #3569121: [meta] Tasks to remove the Shortcut module.
Shortcut will be moved to a contributed project before Drupal 12.0.0 is released.
Comment #6
catch