I hereby claim:
- I am divinedominion on github.
- I am ctietze (https://keybase.io/ctietze) on keybase.
- I have a public key ASAeEXhO_3ukmYArB4BCULSfFFT-rpg6j_aXiWWv_zmBEwo
To claim this, I am signing this object:
#!/usr/bin/env ruby | |
require "rspec" | |
class God | |
def kill!(cell) | |
cell.sacrifice_to self | |
end | |
def surrender(process) |
#!/usr/bin/env ruby | |
# Avoid all the script configuration and use this convenience script instead! | |
# | |
# 1) Put it into the same folder, | |
# 2) run the script: `ruby _execute.rb PATH/TO/THE_NOTE.txt` | |
################## | |
# Configure here # |
I hereby claim:
To claim this, I am signing this object:
(Reply to "Any way to control the priority of subscription callbacks?" ReSwift/ReSwift#404)
ReSwift does not guarantee any subscription callback order. Since ReSwift uses an unordered Set
as its subscription store, there's no reliable way to know when a subscription is invoked.
This implementation detail is hidden by design. If you find yourself wanting to affect the order of subscription callbacks, there's a concept of a sequence waiting to be extracted somehow.
These are the ways out:
import Cocoa | |
import RxSwift | |
import RxCocoa | |
@NSApplicationMain | |
class AppDelegate: NSObject, NSApplicationDelegate { | |
@IBOutlet weak var window: NSWindow! | |
let disposeBag = DisposeBag() |
#!/usr/bin/env ruby | |
require 'optparse' | |
CURRENT_PATH = File.expand_path(File.dirname(__FILE__)) | |
FALLBACK_PATH = File.join(CURRENT_PATH, "..", "build-xcode", "Debug", "include", "libMultiMarkdown", "libMultiMarkdown.h") | |
options = {:mode => :nsenum} | |
OptionParser.new do |parser| | |
parser.banner = "Usage: #{$0} [options] path/to/libMultiMarkdown.h" |
class ExceptionTestCase: XCTestCase { | |
func raisesException() { | |
var exception = NSException(name: NSInternalInconsistencyException, reason: "Testing exceptions", userInfo: nil) | |
XCTAssertThrows({ exception.raise() }) | |
XCTAssertThrowsSpecific({ exception.raise() }, NSInternalInconsistencyException, "Should raise NSInternalInconsistencyException") | |
} | |
} |
struct Foo: ExpressibleByBooleanLiteral { | |
var value: Bool | |
init(booleanLiteral value: BooleanLiteralType) { | |
self.value = value | |
} | |
} | |
func ==(lhs: Foo, rhs: Foo) -> Bool { | |
return lhs.value == rhs.value | |
} |
Title: Focus ReSwift reducers to one state change ID: 201801041611 Tags: #reswift #srp
ReSwift reducers should not have conditional side-effects, changing different states out of convenience. That makes it hard to notice which action changed what. The condition is most of the problem, I think.
An ideal approach would be to have 1 reducer/action pair for each substate change.
When reducers overlap (they touch the same state), this can become a problem. (IncreaseCounter
and DecreaseCounter
are a bad example.) Conditional changes to another substate should be extracted as another action which is dispatched by a Middleware under similar circumstances.
class ModalDialogController: NSWindowController { | |
convenience init() { | |
self.init(windowNibName: "ModalDialogController") | |
} | |
@IBOutlet var closeButton: NSButton! | |
override func windowDidLoad() { |