Automated Drupal 11 compatibility fixes for theme_switcher

Created on 25 March 2024, about 1 year ago
Updated 24 April 2024, about 1 year ago

Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 11.

Changes will periodically be added to this issue that remove deprecated API uses. To stop further changes 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 "ProjectUpdateBotD11" tag from the issue to stop the bot from posting updates.

The changes 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:

  1. Accept automated changes 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 "ProjectUpdateBotD11" tag is left on this issue, new changes 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 changes 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 changes. The bot will still post new changes then if there is a change in the new generated patch compared to the changes that the bot posted last. Those changes are then up to humans to integrate.

  2. Leave open but stop new automated changes.

    If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated changes, remove the "ProjectUpdateBotD11" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated changes again, add back the "ProjectUpdateBotD11" tag.

  3. 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 changes will be posted here.

    If the issue is reopened, then new automated changes will be posted.

    If you are using another issue(s) to work on Drupal 11 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

  1. Apply the latest patch in the comments by Project Update Bot โ†’ or human contributors that made it better.
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.

Using the merge request

  1. Review the merge request and test it.
  2. Thoroughly test the changes. These changes are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the merge request, create a new branch and merge request and work from there.

Warning: The 'project-update-bot-only' branch will always be overwritten. Do not work in that branch!

Providing feedback

If there are problems with one of the changes 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 โ†’ .

๐Ÿ“Œ Task
Status

Needs review

Version

2.0

Component

Code

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @project update bot
  • Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.2 & MySQL 8
    last update about 1 year ago
    Waiting for branch to pass
  • This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.

    It is important that any automated tests available are run and that you manually test the changes.

    Drupal 11 Compatibility

    According to the Upgrade Status module โ†’ these changes make this module compatible with Drupal 11! ๐ŸŽ‰
    Therefore these changes update the info.yml file for Drupal 11 compatibility.

    Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot โ†’ to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

    Debug information

    Bot run #11-127659

    These packages were used to generate the fixes:

    1. drupal/upgrade_status: 4.1.0
    2. mglaman/phpstan-drupal: 1.2.9
    3. palantirnet/drupal-rector: 0.20.1
  • Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.2 & MySQL 8
    last update about 1 year ago
    Waiting for branch to pass
  • First commit to issue fork.
  • Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.2 & MySQL 8
    last update about 1 year ago
    Waiting for branch to pass
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States mradcliffe USA

    I was evaluating the module and noticed the Automated Tests was setup, but no tests were added, so I created a new branch in the issue fork to add a simple test to switchover to Gitlab CI, which needs to be done soon. Hopefully it works.

  • Pipeline finished with Failed
    about 1 year ago
    Total: 139s
    #155441
  • Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.2 & MySQL 8
    last update about 1 year ago
    Waiting for branch to pass
  • Pipeline finished with Failed
    about 1 year ago
    Total: 139s
    #155448
  • Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.2 & MySQL 8
    last update about 1 year ago
    Waiting for branch to pass
  • Pipeline finished with Failed
    about 1 year ago
    Total: 148s
    #155452
  • Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.2 & MySQL 8
    last update about 1 year ago
    Waiting for branch to pass
  • Pipeline finished with Failed
    about 1 year ago
    Total: 140s
    #155462
  • Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.2 & MySQL 8
    last update about 1 year ago
    Waiting for branch to pass
  • Pipeline finished with Success
    about 1 year ago
    Total: 229s
    #155474
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States mradcliffe USA

    Test passes now on both Drupal 10 and Drupal 11.

  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Anybody Porta Westfalica

    D11 is out!

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States BenStallings

    I'm not able to install MR!8 for some reason -- composer can't seem to find the 3434980-gitlabci-dev branch in the fork.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States mradcliffe USA

    I was able to clone the fork and branch successfully on a new DrupalPod instance.

    gitpod /workspace/drupalpod/repos/theme_switcher (3434980-gitlabci) $ git status
    On branch 3434980-gitlabci
    Your branch is up to date with 'theme_switcher-3434980/3434980-gitlabci'.
    
    nothing to commit, working tree clean
    gitpod /workspace/drupalpod/repos/theme_switcher (3434980-gitlabci) $ git remote -vvv
    origin  https://git.drupalcode.org/project/theme_switcher.git (fetch)
    origin  https://git.drupalcode.org/project/theme_switcher.git (push)
    theme_switcher-3434980  https://git.drupalcode.org/issue/theme_switcher-3434980.git (fetch)
    theme_switcher-3434980  https://git.drupalcode.org/issue/theme_switcher-3434980.git (push)
    

    I'll merge origin/2.x and push to the fork. Hopefully that helps.

  • Pipeline finished with Success
    9 months ago
    Total: 133s
    #249625
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States BenStallings

    No luck, mradcliffe... with my composer.json repositories set up like so

            {
                "type": "vcs",
                "url": "https://git.drupalcode.org/issue/theme_switcher-3434980.git"
            },
            {
                "type": "composer",
                "url": "https://packages.drupal.org/8"
            }
    

    I get

    $ composer require drupal/theme_switcher:3434980-gitlabci-dev
    Your requirements could not be resolved to an installable set of packages.
    Problem 1
    - Root composer.json requires drupal/theme_switcher 3434980-gitlabci-dev, found drupal/theme_switcher[dev-8.x-1.x] but it does not match the constraint.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States mradcliffe USA

    Oh, you're trying to download the module from the fork? This is a composer issue rather than a git issue. The branch and issue fork exist in git.

    But it would be easier to test the issue fork in DrupalPod there is a browser extension for DrupalPod that makes this seamless on an issue page.

    When I'm working locally with my own modules, I have the module checked out directly and can add git remotes and checkout branches from issue forks.

  • Status changed to RTBC 6 months ago
  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia rahul1707

    I was able to clone in local. Verified functionality in Drupal 10 and Drupal 11 which looks good to me.
    Upgrade status and PHPCS is also showing no error found.

    Changing status to RTBC.

    theme_switcher-3434980 % git status
    On branch 3434980-gitlabci
    Your branch is up to date with 'origin/3434980-gitlabci'.

    nothing to commit, working tree clean
    theme_switcher-3434980 %

  • ๐Ÿ‡จ๐Ÿ‡ฆCanada Liam Morland Ontario, CA ๐Ÿ‡จ๐Ÿ‡ฆ

    liam morland โ†’ made their first commit to this issueโ€™s fork.

  • Pipeline finished with Success
    6 months ago
    Total: 350s
    #340043
  • ๐Ÿ‡จ๐Ÿ‡ฆCanada Liam Morland Ontario, CA ๐Ÿ‡จ๐Ÿ‡ฆ

    I made some simple coding standards fixes and now tests are fully passing.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States mradcliffe USA

    I wasn't sure if fixing phpcs wold be in scope, but it's great to see fully green. Thank you, @liam morland.

  • ๐Ÿ‡จ๐Ÿ‡ฆCanada Liam Morland Ontario, CA ๐Ÿ‡จ๐Ÿ‡ฆ

    Perhaps the testing-related stuff should be moved to ๐Ÿ“Œ Write basic tests Active .

  • Pipeline finished with Success
    6 months ago
    Total: 135s
    #340080
  • Pipeline finished with Success
    6 months ago
    Total: 139s
    #340117
  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Anybody Porta Westfalica

    Thank you! Merged !8 without sqashing commits!

  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Anybody Porta Westfalica

    Just tagged D11 compatible 2.1.0 release, thank you all! ๐ŸŽ‰

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024