MODx Bug/Feature Tracker and Feature Requests
Welcome to the MODx CMS Tracker. Please choose the appropriate project from the drop down menu and provide as much information as possible regarding your server environment and browser. Thanks!
FS#1046 — The comment about old/duplicaete methods in API.
| Task Type | Feature Request |
|---|---|
| Category | Core Distribution |
| Status | Unconfirmed |
| Assigned To | No-one |
| Operating System | All |
| Severity | High |
|---|---|
| Priority | Normal |
| Reported Version | 0.9.6.1 |
| Due in Version | Undecided |
| Due Date | Undecided |
| Percent Complete |
|
Details
I really hope the comments would be added to old/duplicate methods in API.Though I understand they are for backward compatibility,
there are many old/duplicate methods.
And there are some methods which I guess it would be extended/changed in the near future.
For example, in DocumentParser class,
I guess getExtTable***/getIntTable***() are old methods, they would be integrated in DBAPI class.
And getParent() would be changed to getDocumentParent(),
getPageInfo() is duplicate method of getDocument(). and more.
I feel MODx is really excellent, and respect whole developers.
Please, add a little comment to method which is old/duplicate one, and having plan to extend/change.
And everyone will be happy, and it will be a little easy that new developers join in MODx that is a really excellent CMS/Framework.
This task depends upon
This task blocks these from closing
affectedRows vs DBAPI:getAffectedRows
changePassword vs changeWebUserPassword
dbClose vs DBAPI::disconnect
dbConnect vs DBAPI::connect
dbQuery vs DBAPI::query
fetchRow vs DBAPI::getRow
getDocGroups vs getUserDocGroups
insertId vs DBAPI::getInsertId
putChunk vs getChunk
recordCount vs DBAPI::getRecordCount
regClientHTMLBlock vs regClientScript
regClientStartupHTMLBlock vs regClientStartupScript