-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flatten error by removing ActionError #158
Conversation
[Fix][Carthage] Remove Submodules file
…tings Update project settings to silence warning.
…n for release `3.6.0`
… release + version to
…n for release `3.6.0`
Compatibility with Swift 4.2
Fix build failure on New Build System (default on Xcode 10)
Makes sense – combined with your work on #159, do you think we should target this for the 4.0 branch and release? |
@ashfurrow Yeah, this is breaking changes, I will have to add changelog for this before merging it in 4.0. |
Makes sense – should we update the 4.0 branch, and then change this PR to point to that branch? |
This PR requires the PR #160 to be merged first |
Cool. Once this is merged, and |
# Conflicts: # Changelog.md # Readme.md
Should I merge this @ashfurrow ? |
Hey @dangthaison91 I think you wrongly created this PR with a weird rebase - look at the commits, there are 42 including other people's not just yours. Please don't merge without a review, since this repo is actually commonly used by people it's critical people will be able to review any breaking changes such as these. |
Hmm, should I close this PR and create another one @freak4pc ? |
@dangthaison91 that sounds like a good idea – let me know if you run into git trouble. |
Sure, whatever’s easier for you.
Either fix this PR with a rebase or start a new one which might be more
straightforward.
…--
Shai Mishali
On October 22, 2018 at 23:14:58, (Alfred) ***@***.***) wrote:
Hmm, should I close this PR and create another one @freak4pc
<https://github.com/freak4pc> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#158 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAk7lFFFV54Yz4qRWCQHuqjdwiDn6afKks5unidCgaJpZM4XcztE>
.
|
I really sorry for a long time not active. This replaces PR for #138 and will resolve #119 (original by @bobgodwinx )
After referring Action's implementation from ReactiveSwift, I decide to add
disabledErrors: Observable<Error>
and removeActionError
. This will make breaking change but will help end users avoid misunderstand between.errors/.underlyingErrors
and.executionErrors
from the original proposal. I addActionDisabledError
for better debugging.What do you think @bobgodwinx