evermeer / AlamofireJsonToObjects

An Alamofire extension which converts JSON response data into swift objects using EVReflection
Other
161 stars 28 forks source link

Incorrect arguments label in call #36

Closed Dbigshooter closed 8 years ago

Dbigshooter commented 8 years ago

Hi there,

I just updated my podfile to use the main branch instead of the Swift3, and now I'm facing several instances of the same error.

"Incorrect argument label in call (have 'dictionary:', expected 'coder:')"

This error occurs in both line 61 and 125.

evermeer commented 8 years ago

Do you mean you have a compile error in one of the EVReflection files? Is it in EVReflection.swift?

I'm sure that should not happen. Are you on XCode 8.1? Could you try doing a clean build?

If that does not help, could you try this: remove EVReflection from your pod file, do a pod update so that it will be removed from your workspace, then add it back to the pod file and do a pod update again.

Yesterday I pushed an update to JSONShootout so that it will also test EVReflection. It's using the latest version and I did not get any compiler issues. See https://github.com/evermeer/JSONShootout

Dbigshooter commented 8 years ago

The error occours in AlamofireJsonToObjects.swift, but I'll try the things you said later.

evermeer commented 8 years ago

Ah.. I see there is a problem in AlamoFire. I will try to fix that now...

Dbigshooter commented 8 years ago

@evermeer Sounds awesome! Much appreciated!

evermeer commented 8 years ago

I just pushed a fix for this to GitHub and Cocoapods

Alegero commented 7 years ago

Issue is still reproducible.

evermeer commented 7 years ago

@Alegero Could you please switch to the pod EVReflection/Alamofire since it's maintained actively.

Did you add an import AlamofireJsonToObjects?

Alegero commented 7 years ago

Hi, thanks for tthe answer.

I have switched to EVReflection/Alamofire, but import AlamofireJsonToObjects return error now - “no such module AlamofireJsonToObjects”

On Apr 6, 2017, at 5:02 PM, Edwin Vermeer notifications@github.com wrote:

@Alegero https://github.com/Alegero Could you please switch to the pod EVReflection/Alamofire since it's maintained actively.

Did you add an import AlamofireJsonToObjects?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/evermeer/AlamofireJsonToObjects/issues/36#issuecomment-292184089, or mute the thread https://github.com/notifications/unsubscribe-auth/AZgQbc-C0ZAMfesdyrLhMT8F-MQ_4xftks5rtPCGgaJpZM4Klmdx.

evermeer commented 7 years ago

That's correct, with EVReflection/Alamofire it should be: import EVReflection

pizzimathy commented 7 years ago

I have a similar issue with the EVReflection/XML extension. Using this in conjunction with Alamofire, I have this code:

import Alamofire
import EVReflection
...
class Laundry: EVObject {
    var school_name: String?
    var laundry_rooms: [Room] = [];
}
...
class http {
    class func get(view: DataViewController) {
        if view.isXML {
            Alamofire.request(view.uri).responseData{ response in
                if let data = response.data, let xml = String(data: data, encoding: .utf8) {
                    let laundry = Laundry(xml: xml);
                }
            }
        ...
    }
}

Xcode throws an error when it tries to compile Laundry(xml: xml), as in the example on evermeer/EVReflection, saying that I have an incorrect argument label xml: and that coder: is expected.

I have installed EVReflection/XML by including pod EVReflection/XML in my podfile and have gone through the resolution steps outlined in other peoples' issues. Any help is greatly appreciated. Edit: I have posted this in evermeer/EVReflection.

evermeer commented 7 years ago

@apizzimenti Oeps, sorry, quite some time ago I added some parameters and changed this one to make clear what kind of xml is used. But did not update the documentation (it now is). You should now use:

let laundry = Laundry(xmlString: xml)

pizzimathy commented 7 years ago

Wonderful. Thank you!