Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Symfony 8.2: object mapper feature probe loads deprecated translation command

Open Beginner friendly
  • Is something wrong?
#8,626 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
php, symfony
Domain
api, backend

Research direction

Start in ApiPlatformExtension and reproduce the warning by installing symfony/object-mapper with Symfony 8.2-dev, clearing the cache, and running debug:container --deprecations. Review the regression test that loads the extension with the new command available. Done means the new command namespace is preferred, the older class remains a fallback, and the legacy deprecation is not emitted.

Written by the indexing model from the issue text.

Description

With API Platform 5.0.1 and Symfony 8.2-dev, compiling the application emits a deprecation for Symfony\Bundle\FrameworkBundle\Command\TranslationExtractCommand.

ApiPlatformExtension uses class_exists(TranslationExtractCommand::class) as part of its object-mapper availability gate. Symfony 8.2 moved this command into Symfony\Component\Translation\Command; probing the FrameworkBundle compatibility class autoloads its deprecation even though the command is not used.

Reproduce by installing symfony/object-mapper alongside Symfony 8.2-dev and API Platform, clearing the application cache, and running debug:container --deprecations.

A regression test loading the extension with the new command available confirms that the legacy command is loaded before the fix. Checking the new namespace first, with the existing class as a fallback for older Symfony versions, avoids the warning while retaining object-mapper configuration.

Dominant language
PHP
Stars
2.6k
Forks
984
Avg merge
1d 9h
Merged PRs (30d)
87

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from api-platform/core

All issues in api-platform/core

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.