Skip to content

[Feature request] Use omegaconf or hydra for the config system #1415

@yzhao30

Description

@yzhao30

Is there a plan to use Omegaconf or Hydra for the configuration system?

The current .toml-based configuration system is simple but verbose: it does not support configuration inheritance or composition, which prevents config reuse.

If this is needed, I am interested in contributing an alternative configuration solution based on Omegaconf.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions