Re: [extremeprogramming] About placing configuration defaults

As I wrote before, the biggest problem I have encountered with complex
configuration/options is that some combinations are contradictory (or could
represent situations for which there is currently no good business case to
support).  That is why I believe a rules engine (technically, also Turing
complete) instead of an open-ended programming language can often be the
best choice for pre-processing them coherently when they change (or at
startup).

On Thu, Nov 21, 2019 at 11:52 AM George Paci <[email protected]> wrote:

> One more point:
>
> 6) The earlier your app can validate config values, the better: it can
> immediately complain if something that's supposed to be an int is a
> float (or a non-numeric string); it can detect and complain a bit later
> if some host that's specified is unreachable; if inconsistencies are
> possible in the config file (e.g. two values *must* start with the same
> prefix), it can check for those (though you're better off engineering
> inconsistencies out, e.g. by specifying the prefix separate from the
> rest of each related option).
>
> —George
>
>    The Earth is, in fact, flat for everyday use.
>
>
>
> 
>
>

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

View/Reply Online (#160287): https://groups.io/g/extremeprogramming/message/160287
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]]
-=-=-=-=-=-=-=-=-=-=-=-