We welcome any ideas on bew features and API improvements, as well as pull requests
to avoid encapsulating the whole code into a Promise {} just for that
hi @penso, do you mean
catch doesn't fit your needs? it's typically placed somewhere at the end of the chain, but can also be used in the middle like here: https://github.com/google/promises/blob/master/Tests/PromisesTests/Promise%2BCatchTests.swift#L211
afaik,
tap in PromiseKit also creates a new promise (https://github.com/mxcl/PromiseKit/blob/aea48ea1855f5d82e2dffa6027afce3aab8f3dd7/Sources/Thenable.swift#L259), or you mean something different?
I don't think I need to create a new promise, I just wanted to catch specific errors before continuing.
Another question: https://gist.github.com/penso/276cacdce579fba20b2f7ee9a339a47d ligne 19, using PromiseKit I could use
return .value(document) I believe, using return document doesn't work and I have to add Promises.Promise(), why is that?
Another: if I need run and cast something, using PromiseKit I can do
.map { try foobar(); return true }, using Promises I did it with .then {}, like shown at https://gist.github.com/penso/9c695279e4101fed5dc74c969d5399bf ligne 11. Is that the good way?
