We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hydra 1.0 introduces a package header described in details in this design doc.
The header contains the @package directive, defined as:
@package
@package: _global_ | package-path
_global_
package-path
0.11
oompa.loompa
_group_
foo/bar/zoo.yaml
foo.bar
_name_
zoo
The header format is generic:
# @oompa a.b.c # @loompa: yup x: 10
The resulting header is
{"oompa": "a.b.c", "loompa": "yup"}
Both colon and whitespace are accepted as a separator between the key and the value. Unrecognized header keys (like oompa and loompa) are ignored.
oompa
loompa
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Package Header
Hydra 1.0 introduces a package header described in details in this design doc.
The header contains the
@package
directive, defined as:@package
:_global_
|package-path
_global_
: Global package, this is the default behavior in Hydra0.11
package-path
: Explicit package path, such asoompa.loompa
,the following keywords are replaced at runtime:
_group_
: config group in dot notation:foo/bar/zoo.yaml
->foo.bar
_name_
: config name:foo/bar/zoo.yaml
->zoo
Header format
The header format is generic:
The resulting header is
Both colon and whitespace are accepted as a separator between the key and the value.
Unrecognized header keys (like
oompa
andloompa
) are ignored.The text was updated successfully, but these errors were encountered: