WyriHaximus ยท GitHub

@jsor

Copy link Copy Markdown

Member

@jsor

@WyriHaximus

WyriHaximus

clue

@clue clue left a comment โ€ข

edited

Loading

Copy link Copy Markdown

Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changeset looks reasonable to me, but just one question: Is is common knowledge that Throwable is the base of Exception or should we perhaps make this more explicit? It's my understanding most common use cases would likely reject a promise with a subclass of Exception such as RuntimeException (and family) and it might make sense to keep this as a search keyword in the documentation?

@jsor

Copy link Copy Markdown

Member Author

Good point, i will try to rework the docs ๐Ÿ‘ . But we must make sure to not recommend \Exception as type-declarations in callbacks. Used eg. in otherwise() callbacks, this might lead to uncaught \Error's.

@clue

Copy link Copy Markdown

Member

I concur, adding Throwable as the type hint and adding explicit docs for Exception seems to be the best solution here ๐Ÿ‘

@WyriHaximus

Copy link Copy Markdown

Member

@clue added a short paragraph about Throwable vs Exception.

@WyriHaximus

@WyriHaximus

@WyriHaximus

clue

clue approved these changes Oct 6, 2019

@clue clue left a comment

Copy link Copy Markdown

Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update, changes LGTM! ๐Ÿ’ฏ

@WyriHaximus

Copy link Copy Markdown

Member

๐ŸŽ‰ !

@jsor

@jsor

jsor deleted the throwable-rejection-readme-fixes branch

October 8, 2019 19:29

@valga valga mentioned this pull request

Mar 1, 2020

Closed

Read the original on github.com โ†—