-
Notifications
You must be signed in to change notification settings - Fork 85
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
Documentation for the DI container #67
Conversation
our developer guide would only showcase those classes tagged with in any case this guide would be very useful even for anyone contributing to Piwik core or plugins, and of course to community when writing custom plugins. |
Your comment made me think about this and I actually wrote this doc for Piwik developers, not plugin developers. I think we should hold off as long as we can exposing this to plugins, because as soon as it's exposed we have to keep BC. If it's only used in Piwik (and not 3rd party plugins) it leaves us some times to define best practices on naming container entries (in config files), on how to define entries, etc... We are just starting to use the container with plugins, we should gain more experience before freezing it with BC. Also, So in conclusion, if we want the doc only for core developers we shouldn't merge it yet right? |
Correct, the developer.piwik.org is for Piwik users and plugin developers, so let's not merge it for now |
Now that we have a "Core Development" and a "Plugins / Develop" section can we write one guide for plugin developers under |
|
||
In 3.0, all classes will be constructed with dependency injection. | ||
|
||
### Configuring the container |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think all the part above this section should go into a different page under http://developer.piwik.org/piwik-in-depth as it is quite complicated and not really super relevant for plugin developers.
documented in #356 and targeted for plugin developers |
I don't know if it's the right time to start documenting it. Feedback on the content is appreciated too.