Type Aliasing for DB Type + Fix for Unique Output #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
krshrimali
commented
Jun 28, 2023
Comment on lines
+114
to
+116
| if current_output.contains(key) { | ||
| continue; | ||
| } |
There was a problem hiding this comment.
Passing the output so far and checking if it is already present was the fix here. (since we now process per line, this was missed in the last PR - perks of having no tests 😢 - gotta prioritise it after DB sharding)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
HashMap<String, HashMap<usize, String>>was getting long and redundant).