Yfactorial ObjectiveResource → ObjectiveResource 1.01

Comments and changes to this ticket

• You flagged this item as spam.
  

  jjburka 2009-02-01 17:38:12 UTC

  • Assigned user set to “jjburka”
• 

  Ryan Daigle 2009-02-04 16:54:26 UTC

  Is this done? If not, is it required for 1.0, which we're hoping to announce tomorrow?

• 

  Joshua Vickery 2009-02-04 16:59:22 UTC

  this isn't done, but isn't critical for release

• You flagged this item as spam.
  

  jjburka 2009-02-04 19:10:58 UTC

  • Milestone cleared.
  • Assigned user cleared.

• You flagged this item as spam.
  

  jjburka 2009-02-16 10:13:47 UTC

  • Milestone set to “ObjectiveResource 1.01”
  • Assigned user set to “jjburka”
• 

  Ryan Daigle 2009-02-17 13:34:33 UTC

  (from [aa08bebf52b18782998d5fe7c5c29e98f8625f5f]) [#40] handle multi word class names , [#23] added unit tests for json and xml serialization and deserialization. Improved serialization of NSNumber , added a way to format NSDate serialization http://github.com/yfactorial/obj...

• You flagged this item as spam.
  

  jjburka 2009-02-17 13:39:21 UTC

  • Assigned user changed from “jjburka” to “Joshua Vickery”

  I updated all the unit tests to use supported types. all the unit tests in OR pass with these changes

• You flagged this item as spam.
  

  jjburka 2009-02-17 13:43:54 UTC

  the only big difference between rails xml and ours when serializing is nil objects don't create <element type="type" nil="true"> just <element>

• 

  Joshua Vickery 2009-02-18 12:52:41 UTC

  • Assigned user changed from “Joshua Vickery” to “jjburka”

  all good, see comments on #40

• You flagged this item as spam.
  

  jjburka 2009-02-18 16:42:30 UTC

  • State changed from “new” to “resolved”
• 

  Joshua Vickery 2009-02-19 07:16:56 UTC

  • State changed from “resolved” to “open”

  looks like this broke the sample app: http://groups.google.com/group/o...

• 

  Joshua Vickery 2009-02-19 07:34:02 UTC

  • Assigned user changed from “jjburka” to “Joshua Vickery”
• 

  Joshua Vickery 2009-02-19 07:46:09 UTC

  • Assigned user changed from “Joshua Vickery” to “jjburka”

  I wonder if we shouldn't roll the NSNumber fix back for 1.01 since it changes the way things work in 1.0 pretty significantly.

  We can move it to 1.1 - what do you think James?

• You flagged this item as spam.
  

  jjburka 2009-02-19 09:22:12 UTC

  rollback the isEqualToRemote fix? We honestly should pick either NSString or NSNumber for the id and stick with that. And all the methods expect a NSString so the easiest thing to do would be to use NSString for now

• 

  Joshua Vickery 2009-02-19 09:29:07 UTC

  I mean comment out this: http://github.com/yfactorial/obj...

  until 1.1 and the test that breaks because of it.

  For 1.1 we really need to switch to NSNumber, since that's what Rails provides by default.

• 

  Ryan Daigle 2009-02-19 10:08:58 UTC

  (from [7164876628f8184bd00639dcd4b0371b26da3cc3]) [#23] remove number support http://github.com/yfactorial/obj...

• 

  Ryan Daigle 2009-02-19 10:19:53 UTC

  (from [0321b10a18a157f6169977c5aa91ed7344b460d0]) [#45] cleaned up person , [#23] OS update http://github.com/yfactorial/obj...

• You flagged this item as spam.
  

  jjburka 2009-02-19 10:25:08 UTC

  • Assigned user changed from “jjburka” to “Joshua Vickery”

  sample app works now

• 

  Joshua Vickery 2009-02-20 10:30:39 UTC

  • State changed from “open” to “resolved”