Problem/Motivation
drupal-check on version: 67ae9ec83de40c6021c6ae7a9542bce258ab0bf4
------ -------------------------------------------------
Line views_bulk_operations.drush.inc
------ -------------------------------------------------
89 Call to deprecated function drush_get_option().
93 Call to deprecated function drush_get_option().
103 Call to deprecated function drush_get_option().
112 Call to deprecated function drush_get_option().
118 Call to deprecated function drush_get_option().
174 Call to deprecated function drush_log().
188 Call to deprecated function drush_log().
198 Call to deprecated function drush_log().
203 Call to deprecated function drush_print().
204 Call to deprecated function drush_print().
205 Call to deprecated function drush_print().
------ -------------------------------------------------
[ERROR] Found 12 errors
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #36 | interdiff-29-36.txt | 2.8 KB | edycarreyes99 |
| #36 | vbo-3042613-36.patch | 2.8 KB | edycarreyes99 |
| #29 | 3042613-29.patch | 1.33 KB | manuel garcia |
| #17 | interdiff.txt | 1.76 KB | graber |
| #17 | vbo-3042613-17-d9-readiness.patch | 14.63 KB | graber |
Comments
Comment #2
sergiu stici commentedI changed deprecated methods, please review.
Comment #4
johnvWill you not have backwards compatibility problems removing the precations already?
Or do you expect all installations tht update this module to have the latest drupal version?
Comment #5
sergiu stici commentedI expect the Drupal version to be larger than Drupal 8.5.x because at least
Drupal\Core\TempStore\PrivateTempStoreFactoryis included in the version >= 8.5.xComment #6
manuel garcia commentedBy using the
MessengerTraitwe can avoid BC issues for people extending our classes.Comment #8
graber commentedThanks for this, we should start with
PrivateTempStoreFactoryas it already has its issue (linked).Comment #9
graber commentedNo longer blocked.
Comment #10
manuel garcia commentedRerrolled and fixed a few docblocks for:
Also previous patch docblocks were incorrect in couple of places:
Comment #11
manuel garcia commentedSelf-review, when using ViewsBulkOperationsFormTrait we should use
$this->messenger().Comment #12
joelpittetThanks @Manuel Garcia, looks like things got committed on this branch as it doesn't apply, probably the tempstore stuff. Tagging this to be rerolled.
Tagging for DrupalCon Seattle Friday contribution sprint.
See https://github.com/mglaman/drupal-check/wiki/Drupal-9-Readiness
Slack channel #d9readiness
https://drupal.slack.com/messages/CDDD98AMN
Comment #13
manuel garcia commentedI just tried applying #11 on 8.x-3.x after getting the latest changes, and it applies cleanly :)
Comment #14
manuel garcia commentedComment #15
bjenning commentedI'm just at drupalcon seattle and I tried running drupal-check on patch 11, and I got the following errors:
Line src/Action/ViewsBulkOperationsActionBase.php
16 Class Drupal\views_bulk_operations\Action\ViewsBulkOperationsActionBase implements deprecated interface Drupal\Component\Plugin\ConfigurablePluginInterface.
Line src/Commands/ViewsBulkOperationsCommands.php
Class Drush\Commands\DrushCommands not found and could not be autoloaded.
Comment #16
jerdavisThese implementations are probably not be required. ViewsBulkOperationsActionBase extends ActionBase which extends PluginBase. PluginBase already implements MessengerTrait, so $this->messenger() should already be available.
I think we want this to use $this->messenger() rather than calling the service directly.
Comment #17
graber commentedOk, this will become a bit more tricky.
1. ConfigurablePluginInterface -> ConfigurableInterface: #3048199: Remove deprecated ConfigurablePluginInterface in favour of ConfigurableInterface
2. Class Drush\Commands\DrushCommands not found and could not be autoloaded: needs investigation
3. MessengerTrait in ViewsBulkOperationExampleAction and CancelUserAction: removed
@jerdavis, ViewsBulkOperationsBatch contains static methods, there is no
$thisavailable there.Adding one more reference, the current array-based Batch API is not deprecated but may eventually be.
Setting this to postponed due to 3048199 but we can still commit the work already done if everything is fine with it. Starting from #11 There'll be a commit per patch that introduces something new, I'll also push a feature branch for this.
Comment #21
eelkeblokI think 2 boils down to the particular Drush version Drupal-check can find. I have Drush 10 installed in my setup and instead of complaining about a class it can not find, it says:
I expect these to be marked as deprecated because they are in Drush 10.
Comment #22
eelkeblokAs #3048199: Remove deprecated ConfigurablePluginInterface in favour of ConfigurableInterface is no longer postponed, I guess we can un-postpone this too.
I guess for this the core_version_requirement key will also need to be added, and the core version requirements should also be reflected in composer.json. However, I wonder if that should happen in 4.0, if it's decided that is to happen (see #3048199: Remove deprecated ConfigurablePluginInterface in favour of ConfigurableInterface).
Comment #23
eelkeblokLooks like that issue (#2401797: Introduce a batch builder class to make the batch API easier to use only produced a different way of building the array that will be ultimately fed to batch_set(). Doesn't seem relevant all that much.
Comment #24
maximpodorov commentedglobal $pager_page_array, $pager_total, $pager_total_items are deprecated and should be replaced by PageManager service methods.
Comment #25
graber commentedRe #24, we have that handled in #3056119: Save current data of a pager now.
Comment #26
graber commentedCan someone re-check on the latest dev and update the issue description?
Comment #27
jkswoods commented@Graber issue summary updated.
Comment #28
graber commentedNot bad, thanks :)
Comment #29
manuel garcia commentedThanks @jkswoods for updating the issue summary.
The deprecations on
views_bulk_operations.drush.incare because this is the legacy Drush 8 commands. I think they've already been migrated to Drush 9 (seeViewsBulkOperationsCommands) so its up to the maintainers to decide when to drop support for Drush 8. Looking at this https://docs.drush.org/en/master/install/#drupal-compatibility one could make an argument that any time would in theory be ok.For the time being I have handled the deprecation on
ViewsBulkOperationsActionBasehere (see https://www.drupal.org/node/2946161)Comment #31
jkswoods commentedAs per #29, I think this is good to move in to RTBC.
Comment #32
graber commentedYes, this is actually fixed for now but there may be more deprecations in the future. We may leave it as RTBC so it doesn't dissapear from the issue queue with default filtering.
Comment #33
heddnSeems like we could pick this up in follow-ups. Like #3133476: Add explicit Drush 10 support (since Drush 9 isn't supported by Drupal 9) and #3133476: Add explicit Drush 10 support (since Drush 9 isn't supported by Drupal 9). Maybe this can be marked Fixed again?
Comment #34
graber commentedDrupal 9 is in beta now so no new issues expected. Setting to fixed.
Comment #36
edycarreyes99 commentedfixed 'patch is not applicable', fix drush_log() deprecated code, updated 'drupal/core: ^9' in composer.json file, and added core_version_requirement: ^8 || ^9 for D9 supports.
Comment #37
johnv@edycarreyes99, patch #13 is already committed, as per #30. So please check with latest -dev version.
Also 'closed' tickets are not supposed to be re-opened again.