Fix issue #19: Handle similarly named column headers in merger #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses issue #19 by modifying the
combine
function ininternal/merger.go
to handle similarly named column headers. It introduces a map to store unique headers and their corresponding column indices, and modifies the loop that writes the rows to the output file to merge the data from similarly named columns. It also handles the case where a file does not have a column for a certain header by writing an empty string for that column in the output file.Summary of Changes
combine
function ininternal/merger.go
to handle similarly named column headers.Fixes #19.
To checkout this PR branch, run the following command in your terminal:
To get Sweep to edit this pull request, leave a comment below or in the code. Leaving a comment in the code will only modify the file but commenting below can change the entire PR.