Problem/Motivation

The taxonomy module contains code that was deprecated in Drupal 11.

According to Drupal’s deprecation policy, code deprecated in one major version must be removed in the next major version. Since Drupal 12 is now the active development branch, deprecated Drupal 11 code should be removed.

Steps to reproduce

1. Inspect core/modules/taxonomy.
2. Search for deprecation annotations such as:

@deprecated in drupal:11.x

3. Observe that deprecated implementations are still present.

Expected result: Code deprecated in Drupal 11 should not exist in Drupal 12.

Proposed resolution

Remove all @deprecated in drupal:11.x code from the taxonomy module.

Ensure:

  • All internal usages are updated to supported APIs
  • Test coverage is updated accordingly
  • No references to removed APIs remain in core

---

Remaining tasks

  • Identify all @deprecated in drupal:11.x code in taxonomy.
  • Remove deprecated code.
  • Update tests.
  • Run full test suite.
  • Create or update change record if required.

User interface changes

None.

Introduced terminology

None.

API changes

Yes.

APIs in taxonomy deprecated in Drupal 11 will be removed in Drupal 12. Contributed modules and custom code relying n them must update to supported alternatives.

Issue fork drupal-3573873

Command icon 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:

About issue forks

Comments

smustgrave created an issue. See original summary.

sourav_paul’s picture

sourav_paul
Location Kolkata
commented

@smustgrave I would like to work on this issue, can I pick this one?

smustgrave’s picture

smustgrave commented

Give it a week to see if the maintainer wants to pick up.

smustgrave’s picture

smustgrave commented

Really this one has like one deprecation probably should go to a first time user

smustgrave’s picture

smustgrave commented
Issue tags: +Novice

If no one picks up in 2-3 weeks have at it, if you're looking for one though https://www.drupal.org/project/drupal/issues/3573869 could be tricky

sujal kshatri’s picture

sujal kshatri commented

Can i pick this one?

smustgrave’s picture

smustgrave commented

Rule of thumb I use is if you have less then 2 pages of posts, which is about 100 posts, then novice tagged issues are fine.

So you should be good as you’re not fully up to 100 yet

sujal kshatri’s picture

sujal kshatri commented
Assigned: Unassigned » sujal kshatri
sivaji_ganesh_jojodae’s picture

sivaji_ganesh_jojodae commented
Issue summary: View changes
smustgrave’s picture

smustgrave commented

@ sujal-kshatri wanted to follow up on this one. No worries if you can’t get to it. I’m going to close a number of the small ones out and consolidate but wanted to give ya a chance. Let me know if you have any questions.

FYI you can ignore migration related removal

sujal kshatri’s picture

sujal kshatri commented
Assigned: sujal kshatri » Unassigned

Extremely sorry, I was working on it then my exams came up due to which i'm currently extremely busy,
I'm unassigning myself for time being for someone else to take this up,
my exams will be over after 5 days , if no one picks it up till then then i'll be more than happy to continue my work on it

sivaji_ganesh_jojodae opened merge request !14869

smustgrave’s picture

smustgrave commented
Status: Active » Closed (duplicate)

Combining #3575201: Simple deprecation removal from modules part 1

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.