JSONExport alternatives and similar libraries
Based on the "JSON" category.
Alternatively, view JSONExport alternatives based on common mentions on social networks and blogs.
-
-
-
-
JSONModel
Magical Data Modeling Framework for JSON - allows rapid creation of smart data models. You can use it in your iOS, macOS, watchOS and tvOS apps. -
-
-
Gloss
DISCONTINUED. [Deprecated] A shiny JSON parsing library in Swift :sparkles: Loved by many from 2015-2021 -
-
-
-
TouchJSON
DISCONTINUED. A humane JSON Objective-C un-framework. (TouchJSON has been deprecated - see README) [GET https://api.github.com/repos/TouchCode/TouchJSON: 404 - Not Found // See: https://docs.github.com/rest/repos/repos#get-a-repository] -
-
-
-
CodableAlamofire
DISCONTINUED. An extension for Alamofire that converts JSON data into Decodable objects. -
Genome
A simple, type safe, failure driven mapping library for serializing JSON to models in Swift 3.0 (Supports Linux) -
-
-
Elevate
Elevate is a JSON parsing framework that leverages Swift to make parsing simple, reliable and composable. -
-
-
-
OCMapper
Objective-C library to easily map NSDictionary to model objects, works perfectly with Alamofire. ObjectMapper works similar to GSON -
-
-
-
AlamofireJsonToObjects
An Alamofire extension which converts JSON response data into swift objects using EVReflection -
Jay
DISCONTINUED. Pure-Swift JSON parser & formatter. Fully streamable input and output. Linux & OS X ready. Replacement for NSJSONSerialization. -
-
-
-
InfluxDB โ Built for High-Performance Time Series Workloads
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of JSONExport or a related project?
README
JSONExport
JSONExport is a desktop application for Mac OS X written in Swift. Using JSONExport you will be able to:
- Convert any valid JSON object to a class of one of the currently supported languages.
- Preview the generated content before saving it.
- Include constructors only, utility methods only, both or none.
- Change the root class name.
- Set a class name prefix for the generated classes.
- Set package name for Java files.
Generated Files
Each generated file, besid the getters and setters (for Java) can include:
- A constructor wich accepts an instance of NSDictionary, JSON, JSONObject instance depending on the file language, and the class will use this object to fill its properties data.
- A utility method which converts the class data into a dictionary again.
Currently supported languages
Currently you can convert your JSON object to one of the following languages:
- Java for Android.
- Java for Realm Android.
- GSON for Android
- Swift Classes.
- Swift Classes for SwiftyJSON library.
- Swift Classes for Realm.
- Swift - CoreData.
- Swift Structures.
- Swift Structures for Gloss
- Swift Mappable Classes for (Swift 3) ObjectMapper
- Swift Structures for Unbox
- Objective-C - iOS.
- Objective-C - MAC.
- Objective-C - CoreData.
- Objective-C for Realm iOS.
Screenshot shows JSONExport used for a snippet from Twitter timeline JSON and converting it to Swift-CoreData.
Installation
Kindly clone the project, and build it using xCode 8 and above.
To Do
Support Objective-CDoneSync multible classes with the same name or have the same exact propertiesDoneSupport to parse JSON arrays of objectsDone- Load JSON data from web
Open .json files from JSONExport- Supported languages management editor.
- Beside raw JSON, load the model raw data from plist files as well.
Known Limitations:
- When exporting to subclasses of NSManagedObject, some data types can not be exported. For example core data does not have data type for "array of strings"; in turn, if your JSON contains an array of strings, the exported file will not compile without you fixing the type mismatch.
- When exporting subclasses of RLMObject, you will have to enter the default values of premitive types manually. This is because of dynamic properties limition that prevents you from having an optional premitive type.
- When exporting to CoreData or Realm and you want to use the utility methods, you will need to manually watch for deep relation cycle calls; that is, when you convert an object to dictionary, this object try to convert one of its relation to a dictionary and the relation tries to convert the original object to a dictionary, that will cause a kind of cycle where each object involved calls the other object's toDictionary method infenitly...
- Avoid attempt to model a JSON object with empty values, because JSONExport does not understand empty values and can not guess their types.
- Deep nesting of arrays and objects will not be exported in a proper model files.
Final Note
The application still in its early stage. Please report any issue so I can improve it.
License
JSONExport is available under custom version of MIT license.
*Note that all licence references and agreements mentioned in the JSONExport README section above
are relevant to that project's source code only.