Problem/Motivation
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork notificationswidget-3508957
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #4
bramdriesen@deepali sardana Is the info.yml the only deprecation?
Comment #5
bramdriesenComment #7
bramdriesen@andileco What's the status of your work? 😊 can this be reviewed?
Comment #8
bramdriesenComment #9
andileco commentedTo be honest, I lost track. I think this should definitely be reviewed, though. Thanks for working on this module!
Comment #10
chsdaiguilIs the update of this module to Drupal 11 available?
Comment #11
bramdriesenIt still needs to be tested and checked if all deprecations are fixed
Comment #12
orkutmuratyilmazHello all,
After applying the MR as a patch, the upgrade status module says everything's fine and notifications work, but, phpstan, phpcs & eslint are saying something about low success rates:
https://git.drupalcode.org/issue/notificationswidget-3508957/-/pipelines...
I'm changing the issue status now.
Best,
Orkut
Comment #14
tom kondaI fixed all of ESLint errors.
Comment #15
bramdriesenHi Tom, can you check that what you committed is correct? The diff looks way too large to be just eslint fixes.
Comment #16
tom kondaSorry for my late reply.
I checked my commit and this commit is correct because many of diffs are prettier/prettier errors which are fixed using ESLint with the `--fix` option.
Pipeline log on the previous commit 9a8e23f2:
https://git.drupalcode.org/issue/notificationswidget-3508957/-/jobs/4848...
If no need to fix prettier/prettier errors in this issue, I'll revert prettier/prettier problems.
Comment #17
svendecabooterCould this issue be focussed on getting a D11 release out, while the linting issues get moved to another issue?
The current 2.0.0-alpha7 release also has these code style issues, so it's not a deterioration...
Then people could upgrade to D11, and hopefully the code styling issues could then be fixed soon afterwards...
Or is there a case to be made to take that all together?
Comment #18
bramdriesenHappy to merge if this is tested. Ok for me to fix stylelint etc in another issue.
Comment #20
aren33k commentedI tested this module in our installation, looks OK to me.
Found a small bug/typo and fixed it (Warning: Undefined variable $addtionalEntityTypes in Drupal\notifications_widget\Form\NotificationsWidgetSettingsForm->submitForm() (line 360 of modules/contrib/notificationswidget/src/Form/NotificationsWidgetSettingsForm.php).)
Comment #21
bramdriesenIf the merge conflict is fixed, this can be merged.
Comment #22
tom kondaI fixed merge conflict, please review.
Comment #23
aren33k commentedTested again, works fine for me. MR looks OK.
Comment #24
bramdriesenI spotted one more thing in the JS code.
Comment #26
bramdriesen