fix: add spans for import errors

[tardyp]

Fixes #2

This is my initial attempt at fixing #2.

There are a few design issues that I'd like to discuss:

• the ImportError is arguably part of the api for FileResolver. I choose to rename the original to FileError. Another option is to make the Source and span optional, and have an api like with_source_and_span()
• The find_span function should be an utility function elsewhere. I am not sure where to put it.

Not in scope of #2

• ideally we should report all import error for a file, here we only report the first.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 97.36842% with 1 line in your changes missing coverage. Please review.

Project coverage is 92.62%. Comparing base (5446318) to head (c596c6e).
Report is 1 commits behind head on main.

Files	Patch %	Lines
protox/src/error.rs	96.87%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #80      +/-   ##
==========================================
- Coverage   92.65%   92.62%   -0.04%     
==========================================
  Files          19       19              
  Lines        2384     2415      +31     
==========================================
+ Hits         2209     2237      +28     
- Misses        175      178       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[andrewhickman]

Awesome, thank you!

[tardyp]

Sorry about the fmt and clippy issues. I wanted to post early to get feedback about the design.

Apperently the design was good enough :)

I'd appreciate a release with this fix, so that my users can take advantage of those better error messages.
They already do like a lot the improvement over protoc.

[andrewhickman]

I released version 0.7.1 with this change

[tardyp]

ah! I checked the tags but not the crate.io...

you forgot to push a tag.