[TIMOB-5017] Coverage: Enable get/set autocreated functions for iOS, and allow the blacklist to remove them
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2017-06-07T23:48:15.000+0000 |
Affected Version/s | Release 1.7.2 |
Fix Version/s | n/a |
Components | iOS |
Labels | api, blacklist, coverage |
Reporter | Stephen Tramer |
Assignee | Ingo Muschenetz |
Created | 2011-08-15T16:49:00.000+0000 |
Updated | 2017-06-07T23:48:15.000+0000 |
Description
This bug covers two things:
- We used to create get/set functions for iOS properties automatically in the coverage data, because this is done for us as part of the internal redirect (p.x= and p.setX() are equivalent, p.x (rvalue) and p.getX() are equivalent). This used to be done, so this is probably as easy as uncommenting something in coverage, or checking a property to see if it's get/set, etc. Could possibly include some changes to the AST parser so that it detects RO/RW properties correctly.
- We need to blacklist those get/set functions which should NOT appear as part of the public API - it's debatable whether or not we should only have "some" synonyms, but that is a parity discussion with Android. Until this is resolved, we need to be able to blacklist certain properties as "nogetter" and "nosetter".
Closing ticket due to time passed and lack of progress or input.