Add errors package with metadata support

[sonnes]

No description provided.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.06%. Comparing base (599750f) to head (f69e79a).

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #60      +/-   ##
==========================================
+ Coverage   98.03%   98.06%   +0.03%     
==========================================
  Files          46       47       +1     
  Lines        1067     1084      +17     
==========================================
+ Hits         1046     1063      +17     
  Misses         21       21              

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

[ajatprabha]

Curious about the use-cases, can you add some description on what this solves?

[sonnes]

the idea is to declare generic/package level errors and then wrap them with additional context as they propagate through different layers.

this allows compatibility with errors.Is while still preserving the metadata which can be used to construct detailed error messages, structured logs, detailed error responses, etc.

[sonnes]

i have updated the example https://github.com/gojekfarm/xtools/pull/60/files#diff-1e4aa0f94766e657148fed7d7a4aec95bd44b5bbc4c16bfbb0da3052473f7129 to show a more realistic example

[ajatprabha]

I see, like the fact that the API is quite simple. I remember @sudo-suhas created this, do give it a read, I think there are a bunch of good reads as well in root README.

But I believe you are solving for a simpler use-case, I added the reference for visibility anyway.

[ajatprabha]

Add an output block to make sure this asserts the printed value?

[sonnes]

i tried but the tests become flaky because of the map values are unordered

[sonnes]

I see, like the fact that the API is quite simple. I remember @sudo-suhas created this, do give it a read, I think there are a bunch of good reads as well in root README.

But I believe you are solving for a simpler use-case, I added the reference for visibility anyway.

Yeah, I remember this. The internal xtools has a similar Code based API.