85 1 false 2009-02-25T10:25:07+00:00 5639 9903 2069 namespacing-for-activeresource 1262 8994 open activeresource patch verified 2009-05-19T23:16:48+01:00 5639 Bart ten Brinke Bart ten Brinke Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/2069 2.x If you have an Client object in your Rails app and you want to use ActiveResource to get Clients from another application, then these Client objects have to have exactly the same attributes or ActiveResource will break. Because in a real world situation a lot of people call models in their application by the same name, sometimes you do not want ActiveResource to assume this behaviour. To fix this I added this namespace patch. When a namespace is defined, the ActiveResource resourcename will not be Client, but NameSpaceClient. This will make ActiveResource fall back to it's default 'unknown source' behaviour, making it possible to get remote resources with the same name. If you have an Client object in your Rails app and you want to use ActiveResource to get Clients from another application, then these Client objects have to have exactly the same attributes or ActiveResource will break. Because in a real world situation a lot of people call models in their application by the same name, sometimes you do not want ActiveResource to assume this behaviour. To fix this I added this namespace patch. When a namespace is defined, the ActiveResource resourcename will not be Client, but NameSpaceClient. This will make ActiveResource fall back to it's default 'unknown source' behaviour, making it possible to get remote resources with the same name. <div><p>If you have an Client object in your Rails app and you want to use ActiveResource to get Clients from another application, then these Client objects have to have exactly the same attributes or ActiveResource will break. Because in a real world situation a lot of people call models in their application by the same name, sometimes you do not want ActiveResource to assume this behaviour.</p> <p>To fix this I added this namespace patch. When a namespace is defined, the ActiveResource resourcename will not be Client, but NameSpaceClient. This will make ActiveResource fall back to it's default 'unknown source' behaviour, making it possible to get remote resources with the same name.</p></div> 85 0 If you have an Client object in your Rails app and you want to use ActiveResource to get Clients from another application, then these Client objects have to have exactly the same attributes or ActiveResource will break. Because in a real world situation a lot of people call models in their application by the same name, sometimes you do not want ActiveResource to assume this behaviour. To fix this I added this namespace patch. When a namespace is defined, the ActiveResource resourcename will not be Client, but NameSpaceClient. This will make ActiveResource fall back to it's default 'unknown source' behaviour, making it possible to get remote resources with the same name. <div><p>If you have an Client object in your Rails app and you want to use ActiveResource to get Clients from another application, then these Client objects have to have exactly the same attributes or ActiveResource will break. Because in a real world situation a lot of people call models in their application by the same name, sometimes you do not want ActiveResource to assume this behaviour.</p> <p>To fix this I added this namespace patch. When a namespace is defined, the ActiveResource resourcename will not be Client, but NameSpaceClient. This will make ActiveResource fall back to it's default 'unknown source' behaviour, making it possible to get remote resources with the same name.</p></div> false 2009-02-25T10:25:07+00:00 5639 --- {} 9903 2069 namespacing-for-activeresource 0 8994 new activeresource class name namespacing 2009-02-25T10:25:12+00:00 5639 Bart ten Brinke Bart ten Brinke Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/2069 2.x 85 1 Great! +1 <div><p>Great! +1</p></div> false 2009-02-25T15:28:41+00:00 5639 --- :tag: activeresource class name namespacing 9903 2069 namespacing-for-activeresource 0 8994 new activeresource patch 2009-02-25T15:28:44+00:00 19965 José Valim Bart ten Brinke Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/2069 2.x 85 1 +1 <div><p>+1</p></div> false 2009-02-27T15:13:18+00:00 5639 --- {} 9903 2069 namespacing-for-activeresource 0 8994 new activeresource patch 2009-02-27T15:13:20+00:00 13339 Federico Builes Bart ten Brinke Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/2069 2.x 85 1 It would be really nice if this went in 2.3, together with the XML parser upgrades. It would really make activeresource usable for a lot of people. <div><p>It would be really nice if this went in 2.3, together with the XML parser upgrades. It would really make activeresource usable for a lot of people.</p></div> false 2009-03-10T19:11:35+00:00 5639 --- :tag: activeresource patch 9903 2069 namespacing-for-activeresource 0 8994 new activeresource patch verified 2009-03-10T19:12:14+00:00 5639 Bart ten Brinke Bart ten Brinke Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/2069 2.x 85 1 Bump? <div><p>Bump?</p></div> false 2009-05-19T21:19:57+01:00 5639 --- {} 9903 2069 namespacing-for-activeresource 0 8994 new activeresource patch verified 2009-05-19T21:20:02+01:00 5639 Bart ten Brinke Bart ten Brinke Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/2069 2.x 85 1 Good idea, but the 'namespace' name is too generic. How about localizing the unknown-constant lookup to a single method that subclasses can override to implement whatever behavior they like. <div><p>Good idea, but the 'namespace' name is too generic.</p> <p>How about localizing the unknown-constant lookup to a single method that subclasses can override to implement whatever behavior they like.</p></div> false 2009-05-19T22:03:07+01:00 5639 --- :state: new 9903 2069 namespacing-for-activeresource 0 8994 open activeresource patch verified 2009-05-19T22:03:13+01:00 85 Jeremy Kemper Bart ten Brinke Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/2069 2.x 85 1 Have you got a better suggestion then namespace? Localizing the unkown constant lookup via a method missing is pretty much what is happening in AR right now. Refactoring that is a good idea but goes a lot further then this patch :) <div><p>Have you got a better suggestion then namespace? Localizing the unkown constant lookup via a method missing is pretty much what is happening in AR right now. Refactoring that is a good idea but goes a lot further then this patch :)</p></div> false 2009-05-19T23:16:46+01:00 5639 --- {} 9903 2069 namespacing-for-activeresource 0 8994 open activeresource patch verified 2009-05-19T23:16:48+01:00 5639 Bart ten Brinke Bart ten Brinke Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/2069 2.x 22d6bcc7b6ae55ccd9c9726ee2e6139a7620bee5 text/plain 2009-02-25T10:25:08+00:00 name_spacing_active_resource.diff 92713 4145 5639 http://rails.lighthouseapp.com/attachments/92713/name_spacing_active_resource.diff