- 🇸🇰Slovakia poker10
This function is still in Drupal 10.1.x-dev, see: https://git.drupalcode.org/project/drupal/-/blob/10.1.x/core/lib/Drupal/Core/Updater/Module.php#L84
It seems like it has no direct usages in D10 as well. We need to probably clarify the purpose of this function to decide.
- Status changed to Needs work
over 1 year ago 11:23pm 8 May 2023 - 🇺🇸United States smustgrave
Searching the repo I can't find any reference.
Searched http://grep.xnddx.ru/search?text=getSchemaUpdates&filename= and also didn't find any reference. Probably safe to remove as dead code.
- Assigned to nitin_lama
- last update
over 1 year ago 29,380 pass - 🇮🇳India nitin_lama India
Here's a patch to remove unused code as i cannot find any reference in the core as well.
- Issue was unassigned.
- Status changed to Needs review
over 1 year ago 7:11am 9 May 2023 - Status changed to RTBC
over 1 year ago 1:26pm 9 May 2023 - Status changed to Needs work
over 1 year ago 1:43pm 10 May 2023 - 🇬🇧United Kingdom catch
Before removing something that's unused, we should check whether it's used in contrib (in this case no), but also why it's unused.
I ran
git log -S getSchemaUpdates
and the last mention wascommit 368cf30de0237484dd8eef86069b6649faf66347 Author: webchick <webchick@24967.no-reply.drupal.org> Date: Sat Mar 10 16:23:05 2012 -0800 Issue #1471376 by amateescu: Convert updater.inc to PSR-0.
I went back to the first mention:
git show 6abcc47e25e936aea8 | grep getSchemaUpdates
And it shows the method being added but no usages.
As far as I can tell this was unused when it was added in 2009 and we've just been occasionally moving it around since.
However, it's a public method on a core class so I think we should deprecate it first.
- First commit to issue fork.
- Status changed to Needs review
over 1 year ago 4:48pm 10 May 2023 - last update
over 1 year ago Custom Commands Failed - 🇧🇷Brazil elber Brazil
Hi I deprecated the method and also created a change record, please
- Status changed to Needs work
over 1 year ago 5:06pm 10 May 2023 - 🇺🇸United States smustgrave
If we are going to deprecate it think we should also add trigger_error for it.
- Open on Drupal.org →Environment: PHP 8.1 & MySQL 5.7last update
over 1 year ago Not currently mergeable. - @elber opened merge request.
- last update
over 1 year ago Custom Commands Failed - last update
over 1 year ago Custom Commands Failed - Status changed to Needs review
over 1 year ago 6:15pm 10 May 2023 - Status changed to Needs work
over 1 year ago 11:50pm 10 May 2023 - 🇺🇸United States smustgrave
Should follow how other methods are deprecated
@trigger_error(__METHOD__ . '() is deprecated in drupal:10.1.0 and is removed from drupal:11.0.0. There is no replacement. See https://www.drupal.org/node/3337942 → ', E_USER_DEPRECATED);
- 🇫🇷France andypost
unpublished CR, it needs deprecation test additionally to #16 https://www.drupal.org/about/core/policies/core-change-policies/drupal-d... →
- 🇬🇧United Kingdom catch
We don't need a deprecation test unless there's an actual bc layer with logic in it or similar, when the deprecation is 'just' the phpdoc and trigger_error() we can skip testing for those.
- First commit to issue fork.
- last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago 30,060 pass - Status changed to Needs review
about 1 year ago 6:15am 28 August 2023 - Status changed to RTBC
about 1 year ago 2:28pm 28 August 2023 - 🇺🇸United States smustgrave
Trigger_error looks good, right version.
CR reads well and is with the right branches.
Think this is good to go.
- Status changed to Needs work
about 1 year ago 8:32am 29 August 2023 - 🇬🇧United Kingdom catch
I think this should just be deprecated with no replacement, it's not replaced by hook_update_N(), it's about finding out whether a module has updates that need to be run. No-one is likely to use this since it's very internal to core (except maybe drush but they won't be using this either).
Or we could point people to \Drupal::service('update.update_hook_registry')->getAvailableUpdates
- last update
about 1 year ago 30,062 pass - Status changed to Needs review
about 1 year ago 8:54am 29 August 2023 - 🇳🇿New Zealand quietone
I went with giving people an option, to use
\Drupal::service('update.update_hook_registry')->getAvailableUpdates
. I also updated the CR. - Status changed to RTBC
about 1 year ago 9:25am 29 August 2023 - last update
about 1 year ago 30,129 pass, 2 fail - last update
about 1 year ago 30,135 pass - last update
about 1 year ago 30,136 pass - last update
about 1 year ago 30,136 pass - last update
about 1 year ago 30,146 pass - last update
about 1 year ago 30,146 pass - last update
about 1 year ago 30,148 pass - Status changed to Fixed
about 1 year ago 9:43pm 12 September 2023 -
longwave →
committed 8e42cef1 on 11.x
Issue #3050578 by elber, quietone, nitin_lama, fengtan, smustgrave,...
-
longwave →
committed 8e42cef1 on 11.x
Automatically closed - issue fixed for 2 weeks with no activity.