Skip to content

fix: get correct location data for comments efficiently - #582

Open
jakubbortlik wants to merge 1 commit into
harrisoncramer:developfrom
jakubbortlik:fix-getting-modification-type
Open

fix: get correct location data for comments efficiently#582
jakubbortlik wants to merge 1 commit into
harrisoncramer:developfrom
jakubbortlik:fix-getting-modification-type

Conversation

@jakubbortlik

Copy link
Copy Markdown
Collaborator

This PR fixes #386 and #478.

Apart from sending the correct data to Gitlab (correct line codes, line numbers and modification types), this plugin now creates these data more efficiently, with a single git diff call and with a single iteration through the diff. The PR removes many (often nearly identical) helper functions and adds tests for the newly added or modified functions.

@jakubbortlik

Copy link
Copy Markdown
Collaborator Author

This PR fixes #386 and #478.

Apart from sending the correct data to Gitlab (correct line codes, line numbers and modification types), this plugin now creates these data more efficiently, with a single git diff call and with a single iteration through the diff. The PR removes many (often nearly identical) helper functions and adds tests for the newly added or modified functions.

Follow-ups will include:

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.

Trying to make a comment raises the error: line_code=>["can't be blank", "must be a valid line code"]

1 participant