Rethrow for Better Stack Trace

[dahlbyk]

What kind of change does this PR introduce?
Enhancement

What is the current behavior?
ApiException call stack starts with something like:

   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext()

What is the new behavior?
ApiException call stack starts with something like:

   at Refit.Implementation.Generated.RefitTestsIGitHubApi.<global::Refit-Tests-IGitHubApi-CreateUser>d__29.MoveNext()

Useful for observability to know which request method failed.

What might this PR break?
Folks that depend on the existing stack trace.

Please check if the PR fulfills these requirements

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

Other information:
👋

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (4744780) 90.08% compared to head (817fbfa) 90.08%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1532   +/-   ##
=======================================
  Coverage   90.08%   90.08%           
=======================================
  Files          33       33           
  Lines        1685     1685           
=======================================
  Hits         1518     1518           
  Misses        167      167           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[anaisbetts]

Seems legit but what's with all of these whitespace changes?

[dahlbyk]

Seems legit but what's with all of these whitespace changes?

I knew you'd ask. I can drop the first commit, autoformat was just annoying me so I got them out of the way. The second commit seems useful?

[dahlbyk]

I can drop the first commit

Done

The second commit seems useful?

I kept trimming a trailing space but reverted the rest.

[anaisbetts]

✨

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.