Skip to content

Tags: brianchen003/Argo

Tags

v1.0.1

Toggle v1.0.1's commit message
Bump version to 1.0.1

v1.0.0

Toggle v1.0.0's commit message
Bump version to 1.0.0

v0.4.3

Toggle v0.4.3's commit message

Unverified

The committer email address is not verified.
Bump version: 0.4.3

v0.4.2

Toggle v0.4.2's commit message

Unverified

The committer email address is not verified.
Bump version: 0.4.2

v0.3.4

Toggle v0.3.4's commit message

Unverified

The committer email address is not verified.
Bump version: 0.3.4

v0.4.1

Toggle v0.4.1's commit message

Unverified

The committer email address is not verified.
Bump version: 0.4.1

v0.3.3

Toggle v0.3.3's commit message

Unverified

The committer email address is not verified.
Bump version: 0.3.3

v0.4.0

Toggle v0.4.0's commit message
Update for Swift 1.2

v0.3.2

Toggle v0.3.2's commit message

Unverified

The committer email address is not verified.
Bump version: 0.3.2

v0.3.1

Toggle v0.3.1's commit message

Unverified

The committer email address is not verified.
Use `map` instead of `flatMap` when parsing

`JSONValue.parse` returns a non-optional `JSONValue`. Unfortunately,
because of Swift Magic, Xcode will happily compile when using `flatMap`
with a function that returns a non-optional. This can (but doesn't
always) result in a EXC_BAD_ACCESS error at runtime. Using `map` here is
actually the correct behavior, but should also fix this crash that
people were seeing.