Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skips -primitiveType and -setPrimitiveType: but still generates -primitiveTypeValue and -setPrimitiveTypeValue: #202

Closed
dmdeller opened this issue Jun 5, 2014 · 5 comments
Labels

Comments

@dmdeller
Copy link

dmdeller commented Jun 5, 2014

I came across issue #74 when my app was automatically rejected, so I installed the latest HEAD to get the fix with this command:

brew install --HEAD mogenerator

After, mogenerator no longer generates the problematic -primitiveType and -setPrimitiveType: methods, and outputs warnings to that effect, good. But, it still generates the following two methods:

- (int16_t)primitiveTypeValue {
    NSNumber *result = [self primitiveType];
    return [result shortValue];
}

- (void)setPrimitiveTypeValue:(int16_t)value_ {
    [self setPrimitiveType:@(value_)];
}

Since these refer to the now non-existent methods, it fails to compile.

I was reading at the comments on cd9809d but I couldn't quite figure it out—do I need to do something with templates?

@jkmartin19
Copy link

I'm updating our app and just re-generated our model classes using 1.28. I am running into this issue where the code doesn't compile because it references the non-existent methods primitiveType and setPrimitiveType. What is the best workaround for this issue?

@rentzsch
Copy link
Owner

Nice find. Sorry about that, looking into it now.

@nickynick
Copy link

Any possibility for this fix to be released? Would be nice to be able to get a working version via homebrew :)

@dmdeller
Copy link
Author

@nickynick To get this fix, install with brew install --HEAD mogenerator

@nickynick
Copy link

@dmdeller Ah, thanks! I suspected that something like this exists in homebrew but didn't do a proper lookup.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants