Modified the _config_get function to properly handle nested YAML values. #845
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The OmegaConf's
get
function does not appear to handle nested YAML values as expected.Instead of interpreting the value to the left of
.
as the parent key, it seems to interpret it literally (e.g. searches for a key namedchatgpt.chat_system_template
).The
select
function is able to handle nested values (and searches top-level keys with.
if_CONFIG_KEY
is empty). However, it will not search upward for thekey
, and instead returnsNone
, soget
is still required.ToDo: Move
gpt_config
stuff to a parent class