-
Notifications
You must be signed in to change notification settings - Fork 707
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
Fix LzoTextLine as a TypedSource #921
Conversation
Am testing this internally at Twitter |
@@ -180,15 +180,15 @@ class Job(val args: Args) extends FieldConversions with java.io.Serializable { | |||
|
|||
Config.overwrite(nonStrings, | |||
defaultComparator.map(init.setDefaultComparator) | |||
.getOrElse(init) |
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.
how did this happen with the plugin?
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.
Was wondering that myself. Maybe oscar's patch hadn't run scalariform? I don't think this is such a bad thing. Scalariform will carry us forward in an automated fashion. As long as the diffs aren't huge, shouldn't be a huge risk of merge conflicts.
Can we add a test with the local/platform tests for this? |
Testing with Lzo is very tricky because of the env stuff... |
Ahh, fair enough. Once your happy with it via manual tests, and green will merge. LGTM |
If someone has tested this internally, I say merge. |
Fix LzoTextLine as a TypedSource
LzoTextLine didn't work properly as a TypedSource