-
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
Status Next #239
Status Next #239
Conversation
This time we use our GTStatusDelta objects.
It was never meant for just pathspecs so that name didn't really make any sense at all. This also makes the method slightly more resilient to arrays with more than just strings in them. Generics in Objective C would sure be nice!
This is just in the working directory right now. Need to figure out the best way to change stages in this test.
I like the look of this; the status enumeration was tougher to get right than I'd like in my GUI project, so 👍 for any work to improve that. Seems to still be missing a wrapper to get the status of a particular file ( |
As of yet no… as I thought there would be very few cases where you would actually want to do that. We could go with a |
Removed the |
I haven't reviewed this yet, but you can test staged stuff by manually manipulating |
Ended up using the |
Just noticed I need to document a bunch of stuff in this PR. Chucking |
Conflicts: Classes/GTRepository.h Classes/ObjectiveGit.h External/libextobjc/extobjc/EXTScope.h External/libextobjc/extobjc/EXTScope.m ObjectiveGitFramework.xcodeproj/project.pbxproj
🍍 |
It was all commented out anyway ¬.¬.
We seemed to have 2 completely different codepaths, which depending on which you picked, would lead to a different set of fixtures being used by your test. This was also the root cause of our faulty clean up. Now there is but one set of fixtures and it's set up and torn down properly.
Some test case classes needed to be changed to be GTTestCase but there were no ill-effects. Hell yeah duplicated code --;
OK I yak shaved our horrendous fixture creation and management. Unfortunately that now makes this changeset huge, but hey. @jspahrsummers this is good for another look through now. |
git_strarray strArray = pathSpec.git_strarray; | ||
if (pathSpec != nil) newOptions.pathspec = strArray; | ||
@onExit { | ||
git_strarray_free((git_strarray *)&strArray); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol blocks and const
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not entirely sure what you mean :p
💖 for fixing up the unit tests. |
🚑 |
🚒 |
This brings Objective-Git's wrapping of the status up-to-date with the lurvely new status list API. Adding some unit tests in the process.
We also fix up our horrendous handling of fixtures, including their creation and cleanup.