You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Andrew McKnight (JIRA)" <ji...@apache.org> on 2017/06/10 04:05:20 UTC

[jira] [Commented] (THRIFT-4227) Generate Xcode Core Data model file

    [ https://issues.apache.org/jira/browse/THRIFT-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045368#comment-16045368 ] 

Andrew McKnight commented on THRIFT-4227:
-----------------------------------------

My plan is to copy the XML generator and modify it to match what Xcode writes out when creating a congruent model to a sample Thrift spec. I've already started this.

One thing I know I'll need to do, but haven't actually figured out how yet, is to unwind typedefs to get to the base Thrift types to which they're mapped.

> Generate Xcode Core Data model file
> -----------------------------------
>
>                 Key: THRIFT-4227
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4227
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Cocoa - Compiler
>            Reporter: Andrew McKnight
>            Priority: Minor
>
> As an Apple developer, I'd like to be able to store objects defined in my Thrift spec using the Core Data object relational database system.
> To do this, it is best to generate the XML document that defines the Core Data model. Developers may then use tools like Xcode or mogenerator to generate the actual classes in source code.
> This approach is preferable to directly generating the source code that attempts to subclass NSManaged object, as we can avoid keeping up with language, compiler and Core Data API changes that affect how that source code would be written. By simply stopping with the XML definition, we let Xcode et al handle all the other compatibility concerns.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)