-
Notifications
You must be signed in to change notification settings - Fork 81
Description
Reporter
Ricardo
Is your feature request related to a problem? Please describe.
The parameters have an attribute defaultValueMethods to define which methods (and in which order) to use if the an empty/null value is returned. I now have the situation that I want to override the default order that is used currently (so before the defaultValueMethods come into play). I have a sessionKey that is always filled, but I only want to use that sessionKey if the value-attribute is empty. However, the sessionKey-attribute takes precedence over the value-attribute in the code, so the value-attribute is never used.
Describe the solution you'd like
To be able to determine the order in which parameter attributes are resolved to get a value, so a valueMethods attribute for Parameters. Default value could be the current order (maybe auto-determine which attributes are present so the set value only has those options that are actually present), and last value could be the current defaultValue to maintain compatibility.
Describe alternatives you've considered
N/A
Additional context
N/A
Metadata
Metadata
Assignees
Labels
Type
Projects
Status