Problem/Motivation
Hello project maintainers,
This is an automated issue to help make this module compatible with Drupal 10.
To read more about this effort by the Drupal Association, please read: The project update bot is being refreshed to support Drupal 10 readiness of contributed projects
Patches will periodically be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD10" tag from the issue to stop the bot from posting updates.
The patches will be posted by the Project Update Bot official user account. This account will not receive any issue credit contributions for itself or any company.
Proposed resolution
You have a few options for how to use this issue:
- Accept automated patches until this issue is closed
If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD10" tag is left on this issue, new patches will be posted periodically if new deprecation fixes are needed.
As the Drupal Rector project improves and is able to fix more deprecated API uses, the patches posted here will cover more of the deprecated API uses in the module.
Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot patches. The bot will still post new patches then if there is a change in the new generated patch compared to the patch that the bot posted last. Those changes are then up to humans to integrate.
- Leave open but stop new automated patches.
If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated patches, remove the "ProjectUpdateBotD10" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated patches again, add back the "ProjectUpdateBotD10" tag.
- Close it and don't use it
If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review, Needs work and Reviewed and tested by the community) and no more automated patches will be posted here.
If the issue is reopened, then new automated patches will be posted.
If you are using another issue(s) to work on Drupal 10 compatibility it would be very useful to other contributors to add those issues as "Related issues" when closing this issue.
Remaining tasks
Using the patches
- Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
- Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
- Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.
Providing feedback
If there are problems with one of the patches posted by the Project Update Bot, such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue. For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Project analysis issue queue.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | xnumber.1.x-dev.rector.patch | 15.94 KB | project update bot |
| #8 | interdiff-last-bot.6664737.txt | 422 bytes | project update bot |
| #5 | Screenshot from 2022-07-29 11-02-11.png | 15.48 KB | omkar-pd |
| #2 | xnumber.1.x-dev.rector.patch | 15.75 KB | project update bot |
Issue fork xnumber-3299531
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 #2
project update bot commentedThis is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 10 Compatibility
According to the Upgrade Status module this patch makes this module compatible with Drupal 10! 🎉
This patch updates the
info.ymlfile for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
This patch was created using these packages:
Comment #3
Bushra Shaikh commentedComment #4
Bushra Shaikh commentedComment #5
omkar-pd commentedThis module is Compatible with d10 as per upgrade status and tested this patch on the d10 instance as well and the module is working perfectly fine. Can be moved to RTBC.
Comment #6
drugan commentedHi, guys!
Thanks for contribution. Please make sure all the following errors are fixed so
phpstanwill not complain at least at--level 0:Comment #7
kristen polThanks everyone for participating in porting day!
@drugan Thank you for your detailed report on remaining deprecations that need to be addressed.
Comment #8
project update bot commentedThis is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 10 Compatibility
According to the Upgrade Status module this patch makes this module compatible with Drupal 10! 🎉
This patch updates the
info.ymlfile for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
This patch was created using these packages:
Comment #9
jaydev bhatt commentedI'll work on this issue as a part of Drupal 10 Global Porting Day.
Comment #10
jaydev bhatt commentedneed to check moew rhis moving to NR
Comment #11
jaydev bhatt commentedComment #12
project update bot commentedUpdating bot issue summary.See #3313904: Update project bot templates for RTBC status support and human interaction tips
Comment #13
tyler36 commentedThis module is dependent on
drupal:readmehelpwhich must also be D10 compatable.See Readmehelp Drupal 10 compatibility fixes
Comment #14
kristen polWorking during porting day.
Thanks for the info. Adding #3289247: Automated Drupal 10 compatibility fixes as related issue.
Comment #15
mvonfrie commentedThe dependency on readmehelp (which is not yet Drupal 10 ready) will be removed by #3133932: Remove dependencies on readmehelp and help module.
Comment #17
mvonfrie commentedPending tasks:
PHPstan
--level 0fixesNote: Using configuration file /var/www/html/phpstan.neon.
9/9 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%
------ ------------------------------------------------------------------------------------------
Line src/Tests/XnumberFieldTest.php
------ ------------------------------------------------------------------------------------------
150 Access to an undefined property Drupal\xnumber\Tests\XnumberFieldTest::$url.
489 Call to an undefined method Drupal\xnumber\Tests\XnumberFieldTest::drupalPostAjaxForm().
496 Call to an undefined method Drupal\xnumber\Tests\XnumberFieldTest::drupalPostAjaxForm().
515 Call to an undefined method Drupal\xnumber\Tests\XnumberFieldTest::drupalPostAjaxForm().
520 Call to an undefined method Drupal\xnumber\Tests\XnumberFieldTest::drupalPostAjaxForm().
756 Access to an undefined property Drupal\xnumber\Tests\XnumberFieldTest::$url.
------ ------------------------------------------------------------------------------------------
Resolve depending issues
Update core version requirement
Increase minimum core version requirement to
^9.3 || ^10as 9.3 is the first version supporting PHP 8.1, the minimum for Drupal 10.Comment #18
mvonfrie commentedComment #19
mvonfrie commentedComment #20
mvonfrie commentedThe
Call to an undefined method Drupal\Tests\xnumber\Functional\XnumberFieldTest::drupalPostAjaxForm()occurrences require a major rewrite of the tests, seeIn addition I found used but uninitialized variables in the tests, which also needs to be fixed.
Comment #21
drugan commented@mvonfrie
Let's make it compatible with the
^9.5 || ^10versions.You can
commit --amendand thenpush --forceinto your MR branch.Comment #24
shivam_tiwari commentedComment #25
drugan commentedHi @shivam_tiwari,
The
readmehelpdependency is already fixed on the 2.0.x branch. Additionally, to make the module fully compatible with the core's ^10 version wee need to rewrite theXnumberFieldTest.php. See #17 comment.Because we have the Extended number field types so at the very least we need guarantee the Drupal Core functionality for these types.
For the beginning you can just copy two files below into our Tests folder. Then replace 'integer', 'decimal', 'float' field types in the files for our 'xinteger', 'xdecimal' and 'xfloat'.
The same with the field widget type: 'number' -> 'xnumber'. After that just create a list of what we've extended in the core's functionality and add specific test methods for that in the files:
https://git.drupalcode.org/project/drupal/-/blob/10.1.x/core/modules/fie...
https://git.drupalcode.org/project/drupal/-/blob/10.1.x/core/modules/fie...
Comment #27
drugan commentedThe test is failing:
Comment #28
drugan commentedComment #30
drugan commentedI've ran functional and javascript test on 9.4 and 10.1.2 versions.
I am not sure if there is any sense to merge these changes into 8.x version of the module? If it's true please someone merge upstream and run both tests on the latest 8.x core version to verify that is working there too.
I am going to make 2.0.0-beta1 release tomorrow.
Comment #31
drugan commentedDone.
Thanks everyone!
Comment #33
drugan commented