[TIMOB-24075] Ti.UI: Properties versus methods (getters/setters)
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | Medium |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2019-11-21T18:41:30.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | TiAPI |
Labels | n/a |
Reporter | Creative |
Assignee | Christopher Williams |
Created | 2016-10-25T11:12:28.000+0000 |
Updated | 2019-11-21T18:41:30.000+0000 |
Description
So I have been thinking about this for a while:
Take the page
http://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.ScrollableView-method-scrollToView
The method list shows a lot of bloat due to the inclusion of getters and setters. As far as I know there is no advantage in using properties over the associated getset-method. So I would hereby suggest the removal of these getters and setters, except for cases where it is actually beneficial to use a getter/setter (due to additional parameters perhaps?).
I know this is a breaking change for almost any app out there, but we could start by deprecating these functionalities and removing them from the API docs. Ambiguity is in no way beneficial to understanding and developing Titanium apps.
Thanks for submitting your request. Our engineering team will consider it.
Can we increase this priority?
This was actually deprecated in SDK 8.0.0 (and they are scheduled to be removed in SDK 9.0.0)