Prev: Stdout as IO object
Next: [ANN] Ruby|Web Conference
From: David Masover on 13 Jul 2010 23:24
On Monday, July 12, 2010 06:20:15 pm Michael Granger wrote:
> It will also have any leading
> Ruby-style namespaces stripped, e.g.,
>
> Acme::User -> :user

What's the rationale for stripping namespaces? It looks like hashes are
supported, so the above could be configured with something like:

Configurability.configure_objects({
:user => {:foo => 'bar'},
...
})

It seems to me that I'd want something more like this:

Configurability.configure_objects({
:acme => {
:user => {:foo => 'bar'}
},
...
})

Especially since the whole point of namespacing things is to avoid naming
conflicts, so I could conceivably have:

Configurability.configure_objects({
:acme => {
:user = {:foo => 'bar'},
:anvil => {
:user => 'Wile E. Coyote'
}
},
:examplecorp => {
:user => {:something => 'else'}
}
})

It looks like I could still do something like that by overriding the config
key, but that would flatten it to:

Configurability.configure_objects({
:acme_user => {:foo => 'bar'},
:acme_anvil => {:user => 'Wile E. Coyote'},
:examplecorp_user => {:something => 'else'}
})

 | 
Pages: 1
Prev: Stdout as IO object
Next: [ANN] Ruby|Web Conference