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

Possibly make all policy statements INFO level only #798

Closed
charles-lunarg opened this issue Jan 20, 2022 · 2 comments
Closed

Possibly make all policy statements INFO level only #798

charles-lunarg opened this issue Jan 20, 2022 · 2 comments
Labels
question

Comments

@charles-lunarg
Copy link
Collaborator

@charles-lunarg charles-lunarg commented Jan 20, 2022

While loader policy statements are meant to describe behavior that is suboptimal, the delivery mechanism of using the DebugReport/Utils callback means that they appear as a warning or error when its often not something that can be fixed by the end user of the system.

It could be that each policy statement should be evaluated as to what logging level to use, but I assert that the baseline level should be INFO, not ERROR.

@charles-lunarg
Copy link
Collaborator Author

@charles-lunarg charles-lunarg commented Feb 2, 2022

For now the errors have been made WARNINGs, so it is at least not as bad as it was before.

@charles-lunarg charles-lunarg added the question label Feb 15, 2022
@charles-lunarg
Copy link
Collaborator Author

@charles-lunarg charles-lunarg commented Mar 22, 2022

Going to leave them as warning, since we do want people to see and react to them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question
Projects
None yet
Development

No branches or pull requests

1 participant