We have a long-standing bug where, when a config provider can't provide a configuration for a file, the browse configuration is used to configure that file instead of the intended behavior of falling back to the base configuration. Opening this issue to track restoring that behavior to using the base configuration.
We have a long-standing bug where, when a config provider can't provide a configuration for a file, the browse configuration is used to configure that file instead of the intended behavior of falling back to the base configuration. Opening this issue to track restoring that behavior to using the base configuration.