JASON is a faster JSON deserializer written in Swift.

Properties and functions added for parsing dates with unit tests.

For flexibility, you can let JASON parse the date using a default ISO date formatting string (yyyy-MM-dd'T'HH:mm:ss), or pass in a string format or NSDateFormatter:

let json: JSON = [
    "date1": "2016-04-12T13:29:32",
    "date2": "16/04/2016",
    "date3": "April 10, 2020"
]

json["date1"].dateValue
json["date2"].dateValue("dd-MM-yyyy")

let formatter = NSDateFormatter()
formatter.dateFormat = "MMMM dd, yyyy"

json["date3"].dateValue(formatter)

This is related to discussion #15.

i cant parse json array objects.

my json string is

[{string:value,string:value},{string:value,string:value},{string:value,string:value},{string:value,string:value},{string:value,string:value},{string:value,string:value}]

how can i parse this type of strings?

In the playground try this (branch swift-2.0):

import JASON

let json = JSON("{\"name\": \"foo\"}")
json["name"].stringValue

I'd expect the last line to show "foo". But it doesn't.

Hi, I am currently converting an app from Swift 2 to Swift 3 and was wandering of replacing the existing JSON file with the JASON framework. Here's the issue that I get

When trying to build JASON with latest version of Carthage and Xcode installed, it always fails with this error:

*** Building scheme "JASON iOS" in JASON.xcodeproj
/usr/bin/xcrun xcodebuild -project /Users/milanstevanovic/Developer/ios-cop/Overstats/Overstats/Carthage/Checkouts/JASON/JASON.xcodeproj -scheme "JASON iOS" -configuration Release -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean buildBuild settings from command line:
    BITCODE_GENERATION_MODE = bitcode
    CARTHAGE = YES
    CODE_SIGN_IDENTITY =
    CODE_SIGNING_REQUIRED = NO
    ONLY_ACTIVE_ARCH = NO
    SDKROOT = iphoneos10.0

=== CLEAN TARGET JASON iOS OF PROJECT JASON WITH CONFIGURATION Release ===

Check dependencies
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.

** CLEAN FAILED **


The following build commands failed:
    Check dependencies
(1 failure)
=== BUILD TARGET JASON iOS OF PROJECT JASON WITH CONFIGURATION Release ===

Check dependencies
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.

** BUILD FAILED **


The following build commands failed:
    Check dependencies
(1 failure)
A shell task (/usr/bin/xcrun xcodebuild -project /Users/milanstevanovic/Developer/ios-cop/Overstats/Overstats/Carthage/Checkouts/JASON/JASON.xcodeproj -scheme "JASON iOS" -configuration Release -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build) failed with exit code 65:
** CLEAN FAILED **


The following build commands failed:
    Check dependencies
(1 failure)
** BUILD FAILED **


The following build commands failed:
    Check dependencies
(1 failure)

I'm guessing you left out dates because it would open up a can of worms. I added an extension that works, but is inconsistent with the rest of the API's:

extension JSON {
    public subscript(index: String, dateFormat dateFormat: String) -> NSDate? {
        let formatter = NSDateFormatter()
        formatter.dateFormat = dateFormat

        if let value = self[index].string,
            let date = formatter.dateFromString(value) {
                return date
        }

        return nil
    }
}

Then you use it like this:

date = json["date", dateFormat: "yyyy-MM-dd'T'HH:mm:ss"]

Any thoughts or suggestions on adding support for dates?

About the JSONKeys that if both model have the same properties like 'id' example: struct User { var id = "" } struct Topic { var id = 0 } the User model called id that is a String type the Topic model called id that is a Int type.

now, where in JSONKeys how do define it.

The speed/performance of this library is mentioned twice:

JASON is a faster JSON deserializer written in Swift.

And in the quote:

(...) This is by far the fastest and the most convenient out there (...)

Are there any measurements/benchmarks to back these claims?

So I am trying to use this project in my "pod" and we cannot version the dependency, would be nice if we can make a new version, like 0.3 and host this.

An ideal JSON library will maintain data as an NSDictionary internally rather than force a conversion to a Swift dictionary during init.

On iPhone 5C, JASON runs in 0.002 sec, SwiftyJSON runs in 0.030 sec on a 10,000 item NSDictionary.

JSON data typically originates as an NSDictionary, and converting a large NSDictionary to a Swift dictionary is slow (due to mem copy and casting of every item in the dict).

Type conversions to Swift native types should happen only on key access, thus amortizing the cost (or avoiding the bulk conversion cost in the case where there is no consecutive loop access of every key in the JSON data).

Since NSNumber is converted into Int before being made into Int64, the return value will be wrong on 32 bit architectures (happened on my iPod 5G for example).

(From JASON+Properties.swift)

This code makes the exception:

struct Response: Codable {
  let success: Bool
  let value: Double
}
func testJASON() {
  let string: String =
    """
    {"success":true,"value":100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000≥0}
    """
  let data = string.data(using: .utf8)!
  let json = JASON.JSON(data)
  let val = json["value"].double
  print("\(val)")
}

If you remove one of zeroes in "string" then the decoding will be OK. So the limit is 1e165, after which the decoding fails regardless of Double type can really fit.

I got the following error on linux.

.build/checkouts/JASON/Source/JSONKey.swift:26:8 error: No such module 'CoreGraphics'
import CoreGraphics
       ^

So I remove CoreGraphics dependency for linux.

Running the benchmark with SwiftyJSON 3.1.4 (currently the latest) shows a 25% perf gain with JASON, on-device with a 5C.

Just wanted to make a note for others who might be searching for on-device benchmarks, feel free to close the issue.

Related: the following test case shows a 15x speed improvement with JASON over SwiftyJSON in what I have found to be the most frequent bottleneck in my projects (large NSDictionary data objects): https://github.com/delba/JASON/pull/42

From what I gather by reading #25, the recommended practice is to copy-paste source code instead of using a package manager if you want any of the extensions.

Perhaps the extensions could be supplied through subspecs in CocoaPods? It is how PromiseKit handles extensions https://github.com/mxcl/PromiseKit#extensions.

Carthage does not support subspecs, but you can emulate the behavior by having a separate repository for the optional dependencies. You can still have keep them in one repository by using git submodules.