You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, the call to the parent function is unnecessary because the Bundle class's implementation of the function is empty:
/** * This method can be overridden to register compilation passes, * other extensions, ... * * @return void */publicfunctionbuild(ContainerBuilder$container)
{
}
Also, shouldn't anything related to bundles in documentation of 6.1 and beyond be extending AbstractBundle?
The text was updated successfully, but these errors were encountered:
About your first question, we always call the parent method because even if today might be empty, those parent methods could change in the future, so the code must be ready for that.
About the second question: yes, we should use AbstractBundle everywhere. We did some recent changes related to this (see #19793) but we need to update more examples. Thanks!
In the documentation for Compiler Passes in Bundles, the example shows:
However, the call to the parent function is unnecessary because the Bundle class's implementation of the function is empty:
Also, shouldn't anything related to bundles in documentation of 6.1 and beyond be extending AbstractBundle?
The text was updated successfully, but these errors were encountered: