Unify validation error presentation in Naga CLI and WebGPU compilation messages #6436
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.
Connections
Error
source chainDisplay
output into shader errors #3731.Description
This PR changes the format of validation errors emitted by
naga
CLI and the compilation message API in WebGPU. It changes the presentation of the error in this shader:…which is reported like this in Naga CLI:
…and, particularly badly and motivating this PR, like this in consumers of the compilation message API in WebGPU:
…to this in both contexts:
Testing
I have validated the output of this myself, as is hopefully demonstrated. No tests appeared to need to be updated. If we want snapshot coverage for Naga CLI's output, or our WebGPU API's compilation message items, I believe we should file a follow-up issue to address it.
Checklist
cargo fmt
.taplo format
.cargo clippy
. If applicable, add:--target wasm32-unknown-unknown
--target wasm32-unknown-emscripten
cargo xtask test
to run tests.CHANGELOG.md
. See simple instructions inside file.