New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TIMOB-23812] Handle class properties correctly #65
Conversation
This PR is out of sync with the 1_2_X backport. Please ensure all commits are integrated in both PR's. |
@cheekiatng commented on the jira ticket the special property handling will be removed for 2.0.0. Should i still add the the workaround? |
@janvennemann Hans has reminded me, a better approach to this is that it should be implemented the same way as the 1_2_X back port. And create a separate improvement ticket, titled "Better way to generate properties" or something like that. then a new pull request addressing this new ticket to remove the special property handling, with fixVersion "Release 6.0.0". This way it's much easier to backtrack and keep track of all changes. Thanks for the trouble! |
More of a hacky workaround to maintain api compatibility for all methods that were replaced with properties in iOS 10. This checks against a predefined list of properties and based on that, decides wether a js property or method should be generated.
Approved! |
JIRA: https://jira.appcelerator.org/browse/TIMOB-23812
Adds correct handling for new class level properties introduced with Xcode 8