-
Notifications
You must be signed in to change notification settings - Fork 0
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
Namespace Doc classes #9
Comments
Yep, that's it. We could keep BC with a single class_alias though and increment just a patch. We should also see this as a solution for other components. Use the package namespace as the single point of entry (just had this idea). |
I implement a namespace support into PR #15 as alpha. |
is this solved by the last PR? |
Yep, just a release missing (PEAR and Composer packages). That is why this issue still open =P |
After the pull request accepted from @iannsp into #8 we should now move Doc to its own namespace. This should make Doc version now 0.2.0, roght @alganet ?
The text was updated successfully, but these errors were encountered: