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

Property injection mechanism moved to KVC #151

Merged
merged 1 commit into from
Jan 26, 2014
Merged

Property injection mechanism moved to KVC #151

merged 1 commit into from
Jan 26, 2014

Conversation

alexgarbarev
Copy link
Contributor

Now for primitive types (and some structs like CGRect, CGPoint, etc) we can just use TyphoonPropertyInjectedAsObjectInstance with NSNumber or NSValue as object.

Keep TyphoonPropertyInjectedWithStringRepresentation in place to support xml as is. I thought about removing this injection, but in our xml format we dont know types, so they obtained at runtime.

@jasperblues jasperblues merged commit f4dd070 into appsquickly:master Jan 26, 2014
@jasperblues
Copy link
Member

Great work @alexgarbarev !!!

Rather than deprecate those primitive injectors, I just went ahead and removed them. I think there's move value in having a cleaner API, and its an easy migration. . . there's one tricky one left: injecting a property with a selector, but it can still be done using valueAsText .

Speaking of: valueAsText injection : besides XML, its still sometimes useful to have for:

  • Doing property file style configuration
  • Defining custom type-converters.

. . so we'll definitely keep that one around for a while.

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

Successfully merging this pull request may close these issues.

2 participants