Consider deprecating automatic schema support in favor of extending a config via recursive defaults

[omry]

Hydra 1.0 introduced Structured Configs.
A shortcut was introduced for validating a config file against a schema:
If the name of the config and the name of the schema are the same, the schema is magically used to validate (and populate default values) when loading the config.

This is not very flexible, there are cases where one wants to validate multiple config files against the same schema.
Hydra 1.0 does not have satisfactory support for it.

Hydra 1.1 is adding a new recursive defaults list support, enabling a clean way to achieve that:

db/mysql.yaml

defaults:
  - mysql_schema

hostname: localhost
port: 3307

In this example, the schema is stored into the same config group and is being linked with the config file via the defaults list of that file.

In light of this new capability, I am leaning toward deprecating the shortcut introduced in Hydra 1.0 to make things more consistent and simpler to understand.