-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[HttpKernel] Simplifying Bundle/Extension config definition #16669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It is really important that we document this feature. I've heard many people complain that there is too little documentation on how to create bundles. Let me know if you (anyone) needs help. |
I will start writing it as soon as possible. |
Very friendly ping @yceruto :) I realize we don't really properly document bundle extensions/config in the docs at the moment. If you are in doubt what to document or where, feel free to reply/contact us. |
Thanks for pinging me @wouterj! I've already started documenting it, but unfortunately, I haven't found time to finish it. I will do my best to finish it before the final 6.1 release. |
…ceruto, wouterj) This PR was merged into the 6.1 branch. Discussion ---------- [DI] Documenting Abstract Bundle and Extension Fixes symfony#16669 PR symfony/symfony#43701 ping `@Nyholm` `@wouterj` as you were interested in this feature/doc. Any suggestion to improve the wording is more than welcome! --- I also updated other places to be aligned with the best practices doc. I didn't remove the current convention to create bundles/extensions/configurations because they are still valid until 6.4 becomes the last LTS available. However, it's ok for apps using AbstractExtension. Commits ------- 7a24f08 typo c426dbb Fix extension/config paths c85de08 Revert attribute route 558b02e Rewrite the bundle docs a bit more 7cf9bf4 Add warning d0cba72 Remove note after update the feature c2c47a2 Update bundle.rst c93db0b Jules' review 426e289 Documenting Abstract Bundle and Extension
With this great merged PR #16801, I think we can close this issue ? |
The text was updated successfully, but these errors were encountered: