Add orElseRaise syntax for ApplicativeError

[kubukoz]

No description provided.

[codecov-io]

Codecov Report

Merging #2689 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #2689   +/-   ##
=======================================
  Coverage   93.33%   93.33%           
=======================================
  Files         378      378           
  Lines        7723     7724    +1     
  Branches      218      219    +1     
=======================================
+ Hits         7208     7209    +1     
  Misses        515      515           

Flag	Coverage Δ
#scala_version_212	93.38% <100.00%> (+<0.01%)	⬆️
#scala_version_213	93.11% <100.00%> (+<0.01%)	⬆️

Impacted Files	Coverage Δ
.../src/main/scala/cats/syntax/applicativeError.scala	77.77% <100.00%> (+1.30%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c494157...d0bed2b. Read the comment docs.

[ceedubs]

Thanks, @kubukoz. Would you mind adding an sbt-doctest example for this? That would help motivate it and would also probably help with the code coverage drop.

[kailuowang]

This is a nit:
This method seems closer to adaptError to me, except that it ignores the original error.
orElse is usually associated with recovering. We don't have adaptError in ApplicativeError but we probably should (at least in the syntax) related issue is #2685
I have a proposal there. maybe we call this one adaptErrorTo or orRaise?
I also agree that we can use at least a doctest.

[kubukoz]

I'm back on it. orRaise sounds good to me!

[kubukoz]

@kailuowang can we get this to the finish line? :)

[kailuowang]

LGTM. sorry about the delay.