It is most certainly not the case that all users of REMReM would like to have the same default values on the REMReM lookup parameters as the ones currently hard coded in the code. I'd like to see the following parameters having configurable default values in config files(s):
failIfNoneFound
failIfMultipleFound
lookupInExternalERs
lookupLimit
Motivation
To make it possible to control the default behavior of the lookup function towards Event Repository per deployment of REMReM.
Exemplification
The users of some REMReM instances might have most of their lookups done towards the local Event Repository, and therefore lookupInExternalERs could be set to false, while users of other REMReM instances might have most of their lookups done towards external ERs and then they should not need to provide the lookupInExternalERs=True in all their calls to REMReM.
Benefits
Less parameters to be provided by REMReM users in each call made to REMReM
Possible Drawbacks
It is not possible to rely on the default values described in the REMReM documentation on these values, as they can be changed per deployment. That could be mitigated by clear descriptions updated by the teams deploying REMReM.
Description
It is most certainly not the case that all users of REMReM would like to have the same default values on the REMReM lookup parameters as the ones currently hard coded in the code. I'd like to see the following parameters having configurable default values in config files(s): failIfNoneFound failIfMultipleFound lookupInExternalERs lookupLimit
Motivation
To make it possible to control the default behavior of the lookup function towards Event Repository per deployment of REMReM.
Exemplification
The users of some REMReM instances might have most of their lookups done towards the local Event Repository, and therefore lookupInExternalERs could be set to false, while users of other REMReM instances might have most of their lookups done towards external ERs and then they should not need to provide the lookupInExternalERs=True in all their calls to REMReM.
Benefits
Less parameters to be provided by REMReM users in each call made to REMReM
Possible Drawbacks
It is not possible to rely on the default values described in the REMReM documentation on these values, as they can be changed per deployment. That could be mitigated by clear descriptions updated by the teams deploying REMReM.