Avoid method redefinitions in docs by using unique method names for internal hooks
|Reported by:||bpetty||Owned by:||nacin|
API documentation generators include all source files even if, in practice, only one of these files are included per request. Many core pages re-use the same method names for internal hooks which results in redefinitions for the docs, and resulting in missing documentation.
In general, it's good practice to keep these internal global method names as unique as possible anyway to avoid namespace (global scope) clashes since they aren't intended to be used as public API.
Patch coming soon...
Change History (12)
- Cc scribu added
- Component changed from Inline Docs to Administration