Function mergeOptions

mergeOptions takes two ResourceOptions values and produces a new ResourceOptions with the respective properties of opts2 merged over the same properties in opts1. The original options objects will be unchanged.

Conceptually property merging follows these basic rules:

1. if the property is a collection, the final value will be a collection containing the values from each options object.

2. Simple scaler values from opts2 (i.e. strings, numbers, bools) will replace the values of opts1.

3. opts2 can have properties explicitly provided with null or undefined as the value. If explicitly provided, then that will be the final value in the result.

4. For the purposes of merging dependsOn, provider and providers are always treated as collections, even if only a single value was provided.

mergeOptions takes two ResourceOptions values and produces a new ResourceOptions with the respective properties of opts2 merged over the same properties in opts1. The original options objects will be unchanged.

Conceptually property merging follows these basic rules:

1. if the property is a collection, the final value will be a collection containing the values from each options object.

2. Simple scaler values from opts2 (i.e. strings, numbers, bools) will replace the values of opts1.

3. opts2 can have properties explicitly provided with null or undefined as the value. If explicitly provided, then that will be the final value in the result.

4. For the purposes of merging dependsOn, provider and providers are always treated as collections, even if only a single value was provided.

mergeOptions takes two ResourceOptions values and produces a new ResourceOptions with the respective properties of opts2 merged over the same properties in opts1. The original options objects will be unchanged.

Conceptually property merging follows these basic rules:

1. if the property is a collection, the final value will be a collection containing the values from each options object.

2. Simple scaler values from opts2 (i.e. strings, numbers, bools) will replace the values of opts1.

3. opts2 can have properties explicitly provided with null or undefined as the value. If explicitly provided, then that will be the final value in the result.

4. For the purposes of merging dependsOn, provider and providers are always treated as collections, even if only a single value was provided.