-
Notifications
You must be signed in to change notification settings - Fork 12
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
484 error handeling in case of empty yaml block #1024
484 error handeling in case of empty yaml block #1024
Conversation
…warning via user_note.
If there is an empty component in the user runscript: and a
|
Is there a way to prevent the Besides setting What do you think is the better option? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Can go in :-)
You would need to cache all the warnings and notes and dump them all at the same time to cleanly do that. Don't build that.
I would rather throw it away. Then we at least get |
Thank you @pgierz . I now remove the empty components from This is done before all other config files are merged in. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works well, and I'm okay with having a duplication here. I was looking at the code changes that would be needed to avoid the duplication of the warning and I don't think they are worth the time. Ideally this warning will be there for brief time, then people will fix their yaml files and then they won't need to see the double warning anymore.
#bump |
Closes #484