changes looks good.
can you add tests to avoid regression?

@romsharon98 Thanks for the tip about regression.
It got me thinking about what actually needs to be tested.
At this point, the only relevant test case is for core.execution_api_server_url, which is already covered and passing.

If in the future additional defaults are applied, they will be separately tested.
Have any suggestions?

@romsharon98 Thanks for the tip about regression.

It got me thinking about what actually needs to be tested.

At this point, the only relevant test case is for core.execution_api_server_url, which is already covered and passing.

If in the future additional defaults are applied, they will be separately tested.

Have any suggestions?

Just wondering how it's passing before the change..

@romsharon98

Because merge mutates the first map you pass in and then returns that very same map.
deepCopy duplicates the map, and merge then modifies the copy.

I made a few changes to the code:

• Swapped the logic to use a safer deepCopy instead.
• Added a stricter test assertion to check the trailing /.

@romsharon98

Because merge mutates the first map you pass in and then returns that very same map.

deepCopy duplicates the map, and merge then modifies the copy.

I made a few changes to the code:

• Swapped the logic to use a safer deepCopy instead.

• Added a stricter test assertion to check the trailing /.

Thanks for the clarification:)