-
Notifications
You must be signed in to change notification settings - Fork 280
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
Lack of properties #44
Comments
We thought about creating |
I think this would still work if we declared readonly properties, which will give the benefits of KVO (and bindings on the desktop) and still set the backing values with the methods that take an NSError * reference. If you look at the example project I made to demonstrate how to add the framework to a project, I had to do some fiddling in the controller layer to expose commit properties that would have been better off exposed arrt the model layer. But, rather than talk about it, I'll just make some changes and try and persuade you to pull my changes. That is the Open Source Way, isn't it ;) |
Sounds good, I'll wait for the PR :) |
I've just been writing an example project (soon to appear!) using ObjectiveGit.
There seems to be a lack of properties for a lot of the objects. And many manually created KVC type setters that take an NSError** parameter.
That meant that I had to do more work than I needed to to set up Bindings for the UI.
Before I undertake a large refactor of this , is there any reason why properties have been avoided?
The text was updated successfully, but these errors were encountered: