Expose error definitions

[at-wat]

webrtc.DataChannel.OnError(err error) often receives

• abort chunk, with following errors: (User Initiated Abort: Close called).
• sending reset packet in non-established state: state=Closed

which seems be intended results. (Maybe by the recent updates?)

Possible solutions

• Expose base errors (var errErrorName -> var ErrErrorName) for errors.Is()
• Define struct for errors with values for errors.As()
  e.g. errChunk,

  type ErrChunk struct {
    Name string
    Causes []string
  }
  func (e *ErrChunk) Error() {
    var errStr string
    for _, e := range e.Causes {
      errStr += fmt.Sprintf("(%s)", e)
    }
    return fmt.Sprintf("[%s] abort chunk, with following errors: %s", e.Name, errStr)
  }

[at-wat]

webrtc.DataChannel.OnError(err error) often receives

• abort chunk, with following errors: (User Initiated Abort: Close called).
• sending reset packet in non-established state: state=Closed

which seems be intended results. (Maybe by the recent updates?)

#183 seems related

[edaniels]

We're seeing these errors (specifically sending reset packet in non-established state plenty of the time now and are logging them as such. Is there a way to quiet these if they are normal operating errors?

[at-wat]

@jeremija any idea about above error?

[jeremija]

This is most likely as side effect of #183

I'm not sure if we should skip the callback or expose the errors, but exposing the errors makes sense to me as it's a smaller change (easier to reason about).

[at-wat]

Released v1.8.6

[at-wat]

Using exposed errors in my product works as expected now