Adding code gen #188

plivesey · 2016-10-21T21:57:52Z

I've mostly finished all the code for the initial commit. But need some advice/help/more work on a few things:

I haven't been able to test end to end yet. But rebased on master, and should be able to try that now.
I want to output static files as part of the code gen. I can't work out how to do this.
I want to allow for arbritrary parameters on the command line and parse them into the stencil dictionary (as keys and values). Is this possible? I can't work out how to do this.
There's only one test right now which tests all the features in one model. Is this OK? Or do you want more testing?
TODO: Needs docs.

Input:

{
  "type": "UnitTestClass",
  "fields": [
             {"type": "string", "optional": true, "name": "firstName", "doc": "First name of the unit test"},
             {"type": "string", "name": "lastName"},
             {"type": "array", "element": "UnitTestClass", "name": "friends"},
             {"type": "array", "element": "UnitTestClass", "name": "optFriends", "optional": true, "doc": "An optional array"},
             {"type": "int", "name": "age", "optional": true}
             ]
}

Output:

Usage:

// Can initialze with throws init
do {
  let model = try UnitTestClass.make(dictionary: myDictionary)
} catch {}

// Can init with an optional init
let model: UnitTestClass? = UnitTestClass(dictionary: myDictionary)

// Can init with an optional init and an error reporter closure
let model: UnitTestClass? = UnitTestClass(dictionary: myDictionary) { error in
  print(error)
}

// Generated using SwiftGen, by O.Halligon — https://github.com/AliSoftware/SwiftGen

public final class UnitTestClass: DataModel, Equatable {

  // MARK: Instance Variables

  /**
   First name of the unit test
   */
  public let firstName: String?
  public let lastName: String
  public let friends: [UnitTestClass]
  /**
   An optional array
   */
  public let optFriends: [UnitTestClass]?
  public let age: Int?

  // MARK: Initializers

  public init(firstName: String?, lastName: String, friends: [UnitTestClass], optFriends: [UnitTestClass]?, age: Int?) {
    self.firstName = firstName
    self.lastName = lastName
    self.friends = friends
    self.optFriends = optFriends
    self.age = age
  }

  public convenience init?(dictionary: [String: Any]) {
    try? self.init(dictionary: dictionary, error: { _ in })
  }

  public convenience init?(dictionary: [String: Any], error: ((String) throws -> Void)) rethrows {
    try? self.init(dictionary: dictionary as NSDictionary, error: error)
  }

  public convenience init?(dictionary: NSDictionary) {
    try? self.init(dictionary: dictionary, error: { _ in })
  }

  public init?(dictionary: NSDictionary, error: ((String) throws -> Void)) rethrows {
    let parser = Parser(dictionary: dictionary)
    self.firstName = try parser.fetch("firstName", error: error)
    guard let lastName: String = try parser.fetch("lastName", error: error) else {
      try error("Required field 'lastName' is missing from type 'UnitTestClass'")
      return nil
    }
    self.lastName = lastName
    self.friends = try parser.fetch("friends", error: error)
    self.optFriends = try parser.fetch("optFriends", error: error)
    self.age = try parser.fetch("age", error: error)
  }

  public static func make(withDictionary dictionary: [String: Any]) throws -> Self {
    return try make(withDictionary: dictionary as NSDictionary)
  }

  public static func make(withDictionary dictionary: NSDictionary) throws -> Self {
    let model = try self.init(dictionary: dictionary) { error in
      throw NSError(domain: "com.swiftgen.modelParsing", code: 0, userInfo: [ "parseMessage": error ])
    }
    if let model = model {
      return model
    } else {
      throw NSError(domain: "com.swiftgen.modelParsing", code: 0, userInfo: [ "parseMessage": "Model returned nil with no error." ])
    }
  }

  public static func parse(data: Any, error: (String) throws -> Void) rethrows -> UnitTestClass? {
    if let data = data as? NSDictionary {
      return try self.init(dictionary: data, error: error)
    } else {
      try error("Models must be initialized with NSDictionary. Instead, got \(type(of: data))")
      return nil
    }
  }

  // MARK: Data

  public func data() -> [String: Any] {
    var data = [String: Any]()
    data["firstName"] = firstName?.dataRepresentation()
    data["lastName"] = lastName.dataRepresentation()
    data["friends"] = friends.map { $0.dataRepresentation() }
    data["optFriends"] = optFriends?.map { $0.dataRepresentation() }
    data["age"] = age?.dataRepresentation()
    return data
  }

  // MARK: Builder

  public func map(update: (Builder)->()) -> UnitTestClass {
    let builder = Builder(copy: self)
    update(builder)
    return builder.build()
  }

  public final class Builder {
    public var firstName: String?
    public var lastName: String
    public var friends: [UnitTestClass]
    public var optFriends: [UnitTestClass]?
    public var age: Int?

    public init(copy: UnitTestClass) {
      firstName = copy.firstName
      lastName = copy.lastName
      friends = copy.friends
      optFriends = copy.optFriends
      age = copy.age
    }

    public func build() -> UnitTestClass {
      return UnitTestClass(firstName: firstName, lastName: lastName, friends: friends, optFriends: optFriends, age: age)
    }
  }
}

public func ==(lhs: UnitTestClass, rhs: UnitTestClass) -> Bool {
  return lhs.firstName == rhs.firstName && lhs.lastName == rhs.lastName && lhs.friends == rhs.friends && lhs.optFriends == rhs.optFriends && lhs.age == rhs.age
}

plivesey · 2016-11-07T17:07:53Z

Edited the previous comment with the new changes. I think this is ready for review now and merge once I've worked out the problems listed above.

plivesey · 2016-11-07T17:18:03Z

FYI, I also tested this on https://github.com/bwhiteley/JSONShootout for performance and this solution was faster than any solution there. I'll create a pull request for the repo once I've merged in these changes.

AliSoftware · 2016-11-09T22:34:10Z

I'm not sure it makes sense to see that new feature as a command specifically to generate models, rather than seeing it as a generic JSON input parser? And make the command swiftgen json -t model … instead of swiftgen model …?

Haven't had time to review all the code, but I'm not sure to see why your code would only be tied to model generation and not arbitrary content generation?

plivesey · 2016-11-09T22:56:48Z

So, this code takes JSON as an input and produces models. Naming it JSON seems weird, because that's the input not the output. It seems like all the other commands are based on the output. As in:

swiftgen images ./myImagesFile

Will produce an enum of images. Possibly, you're saying this should be able to create anything? Which is sort of true I suppose...but by default, it produces models (if you don't specify a template), so seems more user friendly to name it model?

plivesey · 2016-11-10T18:45:55Z

Update on original issues and @AliSoftware's comment:

Tested end to end. It works!
Added a base command which outputs static code
I want to allow for arbritrary parameters on the command line and parse them into the stencil dictionary (as keys and values). Is this possible? I can't work out how to do this. (Don't need this for this commit. Will do this in a future commit.
The test seems to exersize all the code paths I need to test
Added docs

I think it's ready for review and merge now :D

AliSoftware · 2016-11-10T18:49:25Z

GenumKit/Stencil/Filters.swift


    return strings.joinWithSeparator(", ")
  }
+
+  static func joinAnd(value: Any?) throws -> Any? {


It has been a while since I checked how Stencil evolved and what new features were brought by more recent versions, but I remember that @kylef wanted to implement filters with parameters. In case that already landed we could use that instead of defining a dedicated filter for each joiner string we need!

Yeah, this is unfortunate. However, I can't see anything in the docs or code which suggests parameters are no supported:
https://github.com/kylef/Stencil/blob/master/Sources/Namespace.swift
open func registerFilter(_ name: String, filter: @escaping Filter) {
:/

I've implemented this in master now, you can find an example of implementing a filter with arguments at stencilproject/Stencil@dfd57e9.

It's going to be a few days until I cut a release with this though, there are other things I want to get into this release.

Yay 🎉
@plivesey it's up to you if you prefer to depend on Stencil's master (we've done that before to wait for other dependencies to do a release) or wait a little until it gets official 😉
(Gonna review that once you've adapted this PR accordingly)

@kylef sadly, I can't upgrade stencil because SwiftGen inherits some classes to modify some behavior. Since things aren't open, this won't compile.

Take a look at https://github.com/AliSoftware/SwiftGen/blob/master/GenumKit/Stencil/GenumTemplate.swift

Template and Namespace are both subclassed here. The code seems reasonable to me (so wondering if you'd consider making these open), but wondering if you have other ideas.

Sub-classing template is still possible. I don't see any real reason you would need to subclass namespace, composition > inheritance. The use here could be replaced by a function creating a namespace. Tbh, I think I'll be rehauling part of the extension API in the next version to make it easier to create "components" containing multiple filters/tags.

I've updated to Stencil 0.7.1 in #219.

Got it, and great. I'll apply your PR to mine.

Hmm, not sure why I didn't catch this locally but there is a problem with my PR. I'll try fix it.

Is the problem that Template isn't actually open? Because I'm confused. For me on 0.7.1:

public class Template: ExpressibleByStringLiteral
https://github.com/kylef/Stencil/blob/master/Sources/Template.swift

AliSoftware · 2016-11-10T18:51:23Z

GenumKit/Stencil/Filters.swift

@@ -106,3 +126,83 @@ struct NumFilters {
    return "\(percent)%"
  }
 }
+
+struct ModelParsingFilters {


Aren't all those too specific? Not sure why we can't implement that in the template instead?

So, this took me the longest time to work out. AFAIK, it is impossible to implement them in the template because of the limitations of Stencil. To take them one by one:

parameterList
This one needs to create a list of params like: x: String, y: Int
The main problem here is that there is no trailing ,. This means it's impossible to do in a template alone. So, I decided to use join! But join takes an array as a parameter, so I need to convert my input to an array. This is impossible to do in stencil. Basically, the main functionality which stencil seems to be missing is a map filter. Sadly, you can't just implement a map componenet, because component's are rendered. You need a map filter. But, since filters can't take parameters, you need to implement seperate filters for each map.

equalityList. Basically, the same problem as above. Need to create an array of == statements, and there is no map function.

initializerList yep same thing here too

parameterType This is needed by parameterList and since it occurs so much in the code gen, I decided to make it a filter too. I could remove it as a filter, but I'd still need it as a private function, and doing this means I don't need to reimplement all this code in the template and makes it much easier to read.

The main concern here is that this will grow as people add their own templates. This is unfortunate, but sadly, Stencil just really doesn't support lists well because the lack of a map (oh, how I love map). As people more methods details, we should be able to change these up to be as generic as we need. I tried to keep stuff as generic as possible creating lists for joining and not just outputting strings.

AliSoftware · 2016-11-10T18:53:44Z

swiftgen-cli/base.swift

+import GenumKit
+import Stencil
+
+let baseCommand = command(


Why the need for that command?

swiftgen templates cat json-base already covers outputting the verbatim content of a template…

Ah. I didn't realize that. Perfect.

plivesey · 2016-12-01T17:32:09Z

@AliSoftware I've updated to use a filter with an argument instead of join&&.
Also rebased on master and migrated to swift 3

There is one outstanding issue: I had to manually edit the stencil pod to make template open. Waiting on @kylef to see what to do about that.

AliSoftware · 2016-12-01T17:47:32Z

Ok, cool, thx!

I'm adding the WIP label to wait for #219 to be merged and Stencil to be updated in SwiftGen, so we could then rebase this PR on top of the changes (that would make your PR cleaner and easier to review if it doesn't contain the Stencil pod update along the rest of the changes) and review it then 😉

kylef · 2016-12-01T18:12:35Z

There is one outstanding issue: I had to manually edit the stencil pod to make template open. Waiting on @kylef to see what to do about that.

I'll make a release (0.7.2) which makes Template open soon and update my PR.

kylef · 2016-12-02T01:43:06Z

GenumKit/Stencil/GenumTemplate.swift

+  namespace.registerFilter("int255toFloat", filter: NumFilters.int255toFloat)
+  namespace.registerFilter("percent", filter: NumFilters.percent)
+  namespace.registerFilter("escapeReservedKeywords", filter: StringFilters.escapeReservedKeywords)
+  namespace.registerTag("ifstrequal", parser: StrEqualsNode.parse)


I don't think this tag or the one below would be necessary with Stencil 0.7, you can use the new if statement that takes operators [docs]. For example:

{% if something == "example" %} {% endif %}

{% if something != "example" %} {% endif %}

Got a basic model that almost compiles working

Updating the codgen to fix the comma issue and simplify some things Adding support for more things like Double and optional array

Adding marks to generated code Improving performance by using NSDictionary instead of [String: Any] A bunch of other work

Docs Adding base type Remaining model stuff to JSON Removing added cocoa pods stuff

Removing references to this in the docs Changing the static code generation in the docs to use `swiftgen templates cat model-base > /path/to/output/file`

djbe

I've pushed a small merge with master.

My main issue with this PR is the 2-fase command, more specifically the static template that'll be embedded in SwiftGen. That's just my opinion though, but I'd like to discuss this 😄

The Readme entry could use a bit more work, I've made some small suggestions. Multiple paths is also something worth thinking about now, before we merge and release this (as it'll change the template syntax).

I haven't reviewed the actual template code yet, I'll do that later this weekend.

djbe · 2016-12-17T16:09:05Z

README.md

@@ -12,6 +12,8 @@ SwiftGen is a suite of tools written in Swift to auto-generate Swift code (or an
 * [`enums` for your NSStoryboards and their Scenes](#nsstoryboard)
 * [`enums` for your Colors](#uicolor-and-nscolor).
 * [`enums` for your Fonts](#uifont-and-nsfont).
+* [`classes` for your models](#models)
+* [`any code` for your JSON specs](#json)


This whole any code section seems extraneous to me. I think there should be one section "Parse your json files", and then one subsection in that about parsing models.

djbe · 2016-12-17T16:10:42Z

README.md

@@ -614,8 +616,196 @@ let sameFont = UIFont(font: FontFamily.Helvetica.Bold, size: 16.0) // iOS
 let sameFont = NSFont(font: FontFamily.Helvetica.Bold, size: 16.0) // OS X
 ```

---
+## Models
+


See comment above. I'd rename this to JSON, and a general description about how a user could parse whatever they want using custom templates. Explain that there's a spec variable.

Then add a subsection about model-parsing.

djbe · 2016-12-17T16:17:07Z

README.md

+```sh
+swiftgen json /path/to/model/file -t model
+swiftgen templates cat model-base > /path/to/output/file
+```


I'm not really a fan of having a command that's effectively split into 2 dependent parts. I understand you want to reduce code duplication, and I wholeheartedly agree with that sentiment.

That said, would it be better to move the contents of model-base to a gist or mini-library? There are new swift JSON parsing libraries appearing every minute, and everyone has their preferences about which one to use. I'm just wondering if it's worth adding a static template to SwiftGen just for this.

That's actually how I originally had it but @AliSoftware asked me to change it to this model. I think he didn't want to maintain another cocoapods library? We'd also have several of these if people added their own codegen.

I agree that there are a bunch of JSON parsing libraries appearing, but most are optimized for making the code look pretty instead of actually providing useful functionality. Since we code gen things, being super terse isn't necessary and we can instead provide useful features.

I'd be fine to revert back to doing this as a library though - I don't have particularly strong feelings about it. @AliSoftware what do you think ^^^?

djbe · 2016-12-17T16:18:03Z

README.md

+swiftgen templates cat model-base > /path/to/output/file
+```
+
+This takes a JSON spec and converts it into a model file which supports parsing from a dictionary, converting back into a dictionary, equality, mapping, and three different initialization options.


Make bullet points about what's supported.

djbe · 2016-12-17T16:20:13Z

README.md

+
+The input is a JSON file which creates a spec for the object. The schema is a custom schema but is based off a few standards (AVRO, Pegasus, JSON Schema). The spec takes a type name and a list of fields. Each field specifies it's type, name, whether it's optional and a doc. It can also specify `array` and `element` for an array of elements. The type and element field can be anything. The model generator simply converts it to an uppercase string for the type.
+
+The model template also requires some static code which makes the generated code smaller. This static code is outputed by `swiftgen templates cat model-base > /path/to/output/file`. You should generate this code as well as the model code for each of your JSON specs.


See above comment, this could simply become "Add the line pod 'MyMiniParsingLibrary' to your Podfile or library of choice".

djbe · 2016-12-17T16:22:10Z

README.md

+```
+</details>
+
+## JSON spec


See first comments above, I'd rearrange this.

djbe · 2016-12-17T16:23:01Z

UnitTests/TestSuites/JSONModelTests.swift

+
+    let expected = Fixtures.string(for: "Models-Dir-Basic.swift.out")
+    XCTDiffStrings(result, expected)
+  }


Add more tests:

empty input model

incorrect input model

djbe · 2016-12-17T16:24:49Z

swiftgen-cli/json.swift

+  let parser = JSONFileParser()
+
+  do {
+    try parser.parseFile(path: path)


It might be interesting to rewrite your parser to accept multiple input files, see #213 for more information. If you do, don't forget to add unit tests for those.

djbe · 2016-12-17T16:25:27Z

templates/json-model.stencil

@@ -0,0 +1,120 @@
+// Generated using SwiftGen, by O.Halligon — https://github.com/AliSoftware/SwiftGen
+
+public final class {{ spec.type }}: DataModel, Equatable {


See comment above, would be cool to accept multiple specs.

djbe · 2017-02-27T23:46:57Z

Hi @plivesey, with the latest SwiftGen release we've split the whole project into many sub-parts. If you'd like I can help you get started on reworking this to match the project changes.

The best place to start is with the parser, which'd go in the SwiftGenKit repository. It might be best to open an issue there first though, so we can discuss the scope of this feature, and what would fit in the SwiftGen project and what wouldn't.

hebertialmeida · 2017-08-10T15:40:40Z

@AliSoftware @djbe This was a need that I also had. So as I use RocketData that was created by @plivesey and SwiftGen I arrived here.

I decided to create a project and that satisfy this need, the biggest motivation to create a separated project is to support more languages like Kotlin and Java. I would love to hear what do you think.
https://github.com/hebertialmeida/ModelGen

This is also somehow related to SwiftGen/SwiftGenKit#30 from @Liquidsoul

AliSoftware · 2017-08-10T15:48:26Z

@hebertialmeida Hey, thx for the feedback

the biggest motivation to create a separated project is to support more languages like Kotlin and Java

I'm not sure I understand that rationale? as SwiftGen, despite its name, is capable of generating whatever you like, as it's based on templates. In fact, in a side projects I once used it to generate Java code using a custom template 😉

The next big pressing feature for SwiftGen after the long-awaited 5.0 release tomorrow will be support for Xcode 9 (Swift 4 templates + support for colors in xcassets). Once this lands, we'll probably start working on the support for swiftgen.yml config file, a JSON parser (which will address the current issue) and maybe merging some repos (in light of what splitting in 4 GH repos led to in term of maintenance and speed of introducing new features).

So JSON parsing is definitely on the radar — and the solution will probably be way more simple to implement now, as it's simply gonna be a pass-thru class conforming to Parser protocol which will automatically leverage support for multiple input files, ability to use --param to toggle the generation of the common static code or not, etc.

AliSoftware · 2017-08-10T15:51:10Z

BTW I see that you already implemented the "use an yml file to configure the tool" feature in ModelGen (which is something we definitely want for SwiftGen, there's an issue pending about that somewhere), would love some contribution on that ;)

AliSoftware · 2017-08-10T15:53:23Z

Quickly looking at your SourceCode, and seing it uses SwiftGenKit already 👍 , I think we could indeed share some implementations there, like your JSONParser.swift file is exactly what I had in mind in the first place.

hebertialmeida · 2017-08-10T15:58:16Z

I can definitely try to help with the yml file, I did that for ModelGen and it was simple. I don't have experience with installers, later I want to add it to Homebrew or something to make it easy.

It is built on top of SwiftGenKit and Stencil with Commander already, I have based on SwiftGen and Sourcery 😄

djbe · 2017-08-10T21:50:33Z

Correct me if I'm wrong, but you don't actually use SwiftGenKit, do you? You depend on it, sure, but I don't see you importing it anywhere. You do use StencilSwiftKit though 👍

hebertialmeida · 2017-08-11T00:49:54Z

@djbe OMG, Yeah you are right, sorry about that, I started using it but then I have created my parsers based on it, then I forgot to remove the dependency. 👍

plivesey force-pushed the master branch from a75016f to 8f8bc7a Compare November 7, 2016 16:39

plivesey changed the title ~~Step one for adding code gen~~ Adding code gen Nov 7, 2016

AliSoftware added the type: enhancement label Nov 9, 2016

AliSoftware self-assigned this Nov 9, 2016

AliSoftware requested changes Nov 10, 2016

View reviewed changes

djbe modified the milestone: Next minor (4.1.0) Nov 20, 2016

plivesey force-pushed the master branch from 20e989f to 887c75b Compare December 1, 2016 17:29

AliSoftware added the status: WIP label Dec 1, 2016

kylef reviewed Dec 2, 2016

View reviewed changes

Peter Livesey added 12 commits December 3, 2016 10:10

Morning's work.

b049df2

Got a basic model that almost compiles working

Adding support for arrays, optionals and also a data() method

120551d

Readme

c99751d

Updating to more avrò like scema

1f7f272

Committing the parser files to the project

df85580

Updating the codgen to fix the comma issue and simplify some things Adding support for more things like Double and optional array

Removing some deleted code

abf571c

Reverting ForTag work

94ad8ac

Reverting README changes

6d30a23

Adding unit test out

baca5cd

Adding docs to both the code and the generated code

252f2f3

Adding marks to generated code Improving performance by using NSDictionary instead of [String: Any] A bunch of other work

End to end tests

b690eb0

Docs Adding base type Remaining model stuff to JSON Removing added cocoa pods stuff

Deleting the base command

84e6a9c

Removing references to this in the docs Changing the static code generation in the docs to use `swiftgen templates cat model-base > /path/to/output/file`

scheme entry

4b6baed

djbe requested changes Dec 17, 2016

View reviewed changes

djbe modified the milestones: Next Minor (4.2.0), Next minor (4.1.0) Jan 1, 2017

This was referenced Jan 16, 2017

Add map node SwiftGen/StencilSwiftKit#9

Closed

Add map node SwiftGen/StencilSwiftKit#11

Merged

djbe modified the milestones: 4.2.0 (Great Split), 5.0.0 Feb 15, 2017

djbe mentioned this pull request Mar 24, 2017

Add file names generator (nibs, plists, etc) #284

Closed

djbe mentioned this pull request Apr 16, 2017

Introduce plist command #288

Closed

Liquidsoul added a commit to Liquidsoul/SwiftGen that referenced this pull request May 6, 2017

[codegen] basic port of PR SwiftGen#188 but missing dependencies updates

18600f5

Liquidsoul mentioned this pull request May 6, 2017

Code generation from JSON data SwiftGen/SwiftGenKit#30

Closed

djbe modified the milestones: 5.1.0, 5.0.0, Nice to Have May 8, 2017

johntmcintosh mentioned this pull request May 5, 2018

New Command: Yaml and plist support #379

Merged

djbe closed this in #379 Sep 6, 2018

djbe modified the milestones: Nice to Have, 6.0.0 Jan 26, 2019


		The input is a JSON file which creates a spec for the object. The schema is a custom schema but is based off a few standards (AVRO, Pegasus, JSON Schema). The spec takes a type name and a list of fields. Each field specifies it's type, name, whether it's optional and a doc. It can also specify `array` and `element` for an array of elements. The type and element field can be anything. The model generator simply converts it to an uppercase string for the type.

		The model template also requires some static code which makes the generated code smaller. This static code is outputed by `swiftgen templates cat model-base > /path/to/output/file`. You should generate this code as well as the model code for each of your JSON specs.

		@@ -0,0 +1,120 @@
		// Generated using SwiftGen, by O.Halligon — https://github.com/AliSoftware/SwiftGen

		public final class {{ spec.type }}: DataModel, Equatable {

Adding code gen #188

Adding code gen #188

Conversation

plivesey commented Oct 21, 2016 • edited Loading

plivesey commented Nov 7, 2016

plivesey commented Nov 7, 2016

AliSoftware commented Nov 9, 2016

plivesey commented Nov 9, 2016

plivesey commented Nov 10, 2016

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kylef Dec 1, 2016 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

plivesey commented Dec 1, 2016

AliSoftware commented Dec 1, 2016

kylef commented Dec 1, 2016

kylef Dec 2, 2016 • edited Loading

Choose a reason for hiding this comment

djbe left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

djbe commented Feb 27, 2017

hebertialmeida commented Aug 10, 2017 • edited Loading

AliSoftware commented Aug 10, 2017 • edited Loading

AliSoftware commented Aug 10, 2017

AliSoftware commented Aug 10, 2017

hebertialmeida commented Aug 10, 2017

djbe commented Aug 10, 2017

hebertialmeida commented Aug 11, 2017

plivesey commented Oct 21, 2016 •

edited

Loading

kylef Dec 1, 2016 •

edited

Loading

kylef Dec 2, 2016 •

edited

Loading

hebertialmeida commented Aug 10, 2017 •

edited

Loading

AliSoftware commented Aug 10, 2017 •

edited

Loading