Fix compilation issues in `dictionaryObjectRepresentation` about plank HOT 8 CLOSED

Resolved in #122. Will be in the 1.4 release

from plank.

@maicki I can confirm updating brought dictionaryObjectRepresentation successfully 👍

from plank.

@DreamingInBinary - I fixed a couple of edge case bugs in the implementation on master so I'll be putting out a patch release now (v1.4.1)

from plank.

I'm having this issue with a property of type NSArray<NSNumber /* Float */ *>. Is there any solution or workaround?

Edit:
I updated to v1.2 (I thought I was using it already) and generated the class again, its working now.

from plank.

We've temporarily disabled that method from generating due to issues like the one you've hit. It will be added back as soon as we have time to work though the remaining issues. If you'd like to pick up the task let me know :)

from plank.

I've recently hit an issue (on v 1.3) where a certain schema doesn't generate the - (NSDictionary *)dictionaryRepresentation; message on the generated model. Reading this issue it appears that this was disabled possibly? Thing is, it does generate for the other .json schemas I use.

Is this possibly related to this issue?

{
    "id": "user.json",
    "title": "user",
    "description" : "Schema definition of a User",
    "$schema": "http://json-schema.org/schema#",
    "type": "object",
    "properties": {
        "id" : { "type": "string" },
    	"name" : { "type": "string" },
    	"role" : { "type": "string" },
    	"phoneNumber" : { "type": "string" },
        "avatar" : { "type": "string", "format":"uri" },
	"createdAt" : { "type": "string", "format": "date-time" },
	"updatedAt" : { "type": "string", "format": "date-time" },
	"latitude" : { "type": "integer" },
	"longitude" : { "type": "integer" },
	"isSignificantOther" : { "type": "boolean" },
        "relatedUsers" : { 
		"type": "array",
                        "items": {
                             "type": "string"
                         }
            }
    }
}

from plank.

@DreamingInBinary Hey - what is your exact problem? We had to disable dictionary representation as it caused issue.

That said, we just enabled json dictionary representation again on master. Can you pull master and see if this fixes your issue.

from plank.

I’ll get out a new release soon but you should be able to pull and build the latest master to fix

from plank.