-
Notifications
You must be signed in to change notification settings - Fork 24
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
Not parsing combined diffs correctly #23
Comments
Actually, I just noticed that in the documentation you say "context diff", not "combined". |
Hey! Big fan of the pydriller work, been following the research output for a bit. :) Yes, this is something I think we can add from this example file. I was planning on doing a new release soon anyway. Do you have any example of what you'd expect the output structure to be? Currently each line change would just all be collapsed into one list of changes, but I'm not sure if having the source it came from would be useful or not for your use case. |
Awesome 😄 what I'd need for PyDriller is: |
Apologies for the slow work. Not a lot of free weekends this summer. I promise I started this, but got stuck :-) |
Oh no worries! I know the feeling 😄 |
Didn't get to include this in the 0.0.6 release; primary problem is I think there should be a few new format fields that other formats don't need and the refactor got deep. Did want to make sure the other changes got out to the public though since it's been ... ⌚️ 👀 ... 2.5 years |
Hi @cscorley !
I was looking for a tool to parse combined diff to use inside my tool (https://github.com/ishepard/pydriller), and ended up here. In your documentation you state you can parse the combined diff (
-c
or--cc
option), however I am not able to obtain complete results. Let's make an example. I have this combined diff:If I run:
I obtain:
As you can see,
old_path
is "--cc", that doesn't make sense, and changes are alwaysNone
.The text was updated successfully, but these errors were encountered: