You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally key collisions across multiple configs could combine data, so
multiple values could be generated across configs.
For example, config kevoreilly#1 generates the following:
{"cfg1": {"key": "value1"}
While config kevoreilly#2 generates:
{"cfg1": {"key": "value2"}
And their combined config becomes:
{"cfg1": {"key": ["value1", "value2"]}}
The existing behavior is to let the last config win on key
collisions, resulting instead in:
{"cfg1": {"key": "value2"}}
So reflect that in the new test coverage, and simplify the config update
method by forwarding the cape_name.
0 commit comments