Skip to content
New issue

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

Fix: Moving yaml_decode, and using it in ConfigGroup as well #2317

Merged
merged 2 commits into from
Feb 16, 2023

Conversation

rshade
Copy link
Contributor

@rshade rshade commented Feb 16, 2023

Proposed changes

This moves the fix from: #2156 into ConfigGroup as well. It moves invoke_yaml_decode out of ConfigFile and reuses it in both places.

Related issues (optional)

Fix #2309

@github-actions
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@github-actions
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@rshade rshade enabled auto-merge (squash) February 16, 2023 17:07
@rshade rshade merged commit 623fbbe into master Feb 16, 2023
@rshade rshade deleted the rshade/fix-yaml-decode branch February 16, 2023 17:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ConfigGroup throws NoneType error in python
2 participants