[
https://issues.apache.org/jira/browse/THRIFT-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew McKnight updated THRIFT-4227:
------------------------------------
Description:
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.
*Gameplan:*
(/) Copy XML generator
(/) Output non-nested structs conforming to Core Data model XML DSL
(x) Collections of basic types
(x) Nested structs
(x) Collections of struct types
(x) Unwind typedefs to resolve basic types to map to core data types
(x) Replace enum types with Integer 32 type
(x) Optional means optional
(x) Add option in cocoa/swift generators to suppress struct generation
was:
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.
*Gameplan:*
(/) Copy XML generator
(/) Output non-nested structs conforming to Core Data model XML DSL
(x) Collections of basic types
(x) Nested structs
(x) Collections of struct types
(x) Unwind typedefs to resolve basic types to map to core data types
(x) Replace enum types with Integer 32 type
(x) Optional means optional
> 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.
> *Gameplan:*
> (/) Copy XML generator
> (/) Output non-nested structs conforming to Core Data model XML DSL
> (x) Collections of basic types
> (x) Nested structs
> (x) Collections of struct types
> (x) Unwind typedefs to resolve basic types to map to core data types
> (x) Replace enum types with Integer 32 type
> (x) Optional means optional
> (x) Add option in cocoa/swift generators to suppress struct generation
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
