Feature request: deeply merge_configs

[Jasha10]

Using the new merge_configs option to the ProjectConfig.__init__ method, configs like the following can be merged:

merged({"foo": "bar"}, {"baz": "qux"}) == {"foo": "bar", "baz": "qux"})

However, dictionaries nested more deeply than the toplevel are not merged:

# current behavior:
merged({"inner": {"foo": "bar"}}, {"inner": {"baz": "qux"}}) == {"inner": {"baz": "qux"}})
# left config overwritten by right config

I would expect that nested configuration gets merged instead of being overwritten:

# expected:
merged({"inner": {"foo": "bar"}}, {"inner": {"baz": "qux"}}) == {"inner": {"foo": "bar", "baz": "qux"}})

[Jasha10]

For context: deep merging will be useful for autoimport. Specifically, deep merging will enable the use-case where multiple autoimport config files each specify part of the common_statements mapping.

cc @lyz-code

[dbatten5]

hi @Jasha10 thanks for raising the issue and the pr, i like the proposal. will take a look at the pr now

[dbatten5]

@Jasha10 @lyz-code this should now be available in 1.4.0