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

Possible: Flex recipe is registered under the old package name, imports a missing all.xml, and has a typo'd handler_id

Open
#259 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
php, symfony
Domain
api, backend

Research direction

Inspect recipes/silverbackis/api-components-bundle/2.0 and composer.json:2, then verify the recipe in the running app. Compare the recipe's package name, routing/all.xml reference against routing/all.php, and handler_id with the reported names; done means the confirmed recipe issues no longer prevent it from running and the docs' manual setup is accurate.

Written by the indexing model from the issue text.

Description

Possible finding, not confirmed. This came up during a docs accuracy pass (components-web-app/docs#20–#25) and hasn't been checked in the running app. It may already be handled, or intended. Please verify before acting on it.

recipes/silverbackis/api-components-bundle/2.0 is registered under silverbackis/api-components-bundle, but the package is components-web-app/api-components-bundle (composer.json:2), so it doesn't run. It also imports routing/all.xml (only all.php exists) and uses handler_id: silverback.api_component.… (missing an s?). The docs now tell users to create the files by hand.

Dominant language
PHP
Stars
32
Forks
8
Avg merge
40m
Merged PRs (30d)
133

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 components-web-app/api-components-bundle

All issues in components-web-app/api-components-bundle

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.