Repository navigation
Improve error messages in uxarray/core - #1678
Conversation
ASV BenchmarkingBenchmark Comparison ResultsBenchmarks that have stayed the same:
|
|
Style is reasonable — keep the actionable hints like
|
|
Can you rebase this one? Happy to review once it's clean. |
as per reviewer comments
type(thing) if error message is mainly just reporting type(thing), to give more verbose outputs, but type(thing).__name__ if type(thing) is just one piece of the error message report.
Thank you for the review, and apologies for the delayed response! The notification for this got buried / accidentally marked as "read" without me actually taking a look. Responding to these requests first:
Next I will fix the merge conflicts, and let you know when it is ready for review! |
use data_mapping instead. (data_location was removed from `main`). Also replaces "face_centered" with "face-centered" or with something like "data mapped to faces"; similar for "node_centered" and "edge_centered".
|
I believe it is now ready for review! Resolved merge conflicts, and removed |
Closes #1677 (sub-issue of #1617)
Overview
Makes error messages clearer and more informative throughout uxarray/core. As suggested by #1617 this is attempting to be an exhaustive fix for all desired error message improvements in uxarray/core, while touching nothing outside of uxarray/core.
Tiny expansion of scope: fixes confusing/misleading error types in a few places missed by #1622:
Aside from this tiny expansion of scope there should be no functionality changes; the only differences in this PR are the changes to error message contents.
Additional notes:
PR Checklist
General
Testing & Benchmarking
AI Disclosure
AI Usage: GitHub Copilot's inline code suggestions, some tiny chats with Claude about error message style.