Lack of interest Missing source code documentation (1.2 RC)

This suggestion has been closed automatically because it did not receive enough votes over an extended period of time. If you wish to see this, please search for an open suggestion and, if you don't find any, post a new one.


Well-known member
I am not sure if this qualifies as a "bug", but since this section is also meant for things that "look out of place in XenForo", I thought to mention it here.

Many if not most newly added methods in xF 1.2 RC miss documentation, such as description, @param and @return. This is unfortunate since it makes it much more difficult for developers to understand the code. This is in contrast to xF 1.1.x, where its source code is quite thoroughly documented.

It would be nice if the missing source code documentation were to be added before the final release.
Upvote 3


XenForo moderator
Staff member
A bug by definition is something which causes the software to behave unexpectedly.

I'm not sure this qualifies so really is a suggestion.


Well-known member
Don't have a problem with that. Although - "something that looks out of place" (bug section description) probably depends on the eye of the beholder. :p


Well-known member
I agree. (but it's RC and i hoped to see this till gold^^)

Specially the edithistoryhandler wasted some MINUTES of my life:p (it was because of $_prefix which wasn't implemented (i'm somebody who's just creating the class, extending it from the abstract handler and let the IDE implement all necessary methods.. that's why i would prefer to have abstract getter methods for this => it makes sure that the variables are set...

the same happened me some years ago with the attachment handler and contentIdKey & contentRoute variable which were missing, till i saw the comments in the attachment handler... And because of the missing edithistoryhandler documentation, i was redirected to index till i started the debugger...

Also $_prefix is a stupid name, in some classes / contexts it's prefix, sometimes it's called route or contentroute...... There's often no consistency :/

SORRY for the offtopic:p
Last edited: