Re: [extremeprogramming] About placing configuration defaults

Avi,

Should we really require the customer to have enough insight into the
internal object architecture of the software to be able to guess where a
particular configuration choice is stored?

On Tue, Nov 19, 2019 at 8:25 AM Avi Kessner <[email protected]> wrote:

> My understanding is that the defaults should be placed closest to where
> these things change.
>
> Some defaults should be at the top level, especially defaults related to
> the environment. (base urls, api keys etc)
> Some defaults should be placed where the configuration is being requested,
> especially arguments that are passed in at runtime. (test file name, number
> of interactions, other optional args you might have)
> Wherever someone might be interested in what the default is, try to have
> them searching for it as little as possible.
>
> The less often the value of the config is likely to change, the "higher
> up", I think it should be.
>
> brought to you by the letters A, V, and I
> and the number 47
>
>
> _._,_
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#160233): https://groups.io/g/extremeprogramming/message/160233
Mute This Topic: https://groups.io/mt/60557252/2417047
Group Owner: [email protected]
Unsubscribe: https://groups.io/g/extremeprogramming/leave/4902963/619838065/xyzzy  [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-