-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix deprecated auto application of () to method invocations #1422
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -57,7 +57,7 @@ object XercesValidatorFactory { | |
if (config.hasPath(XercesValidator.name)) | ||
config.getStringList(XercesValidator.name).asScala | ||
else Seq.empty | ||
XercesValidator.fromFiles(schemaFiles) | ||
XercesValidator.fromFiles(schemaFiles.toSeq) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok, so what exactly are the rules about when you must have the "()" and when not? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It turns out Scala 2.13 doesn't always complain about all nullary methods "For reasons of backwards compatibility, Scala 3 for the moment also auto-inserts () for nullary methods that are defined in Scala 2, or that override a method defined in Scala 2." Which toSeq seems to fall under, shall I add it to toSeq? https://docs.scala-lang.org/scala3/reference/dropped-features/auto-apply.html |
||
} | ||
|
||
def makeConfig(uris: Seq[String]): Config = { | ||
|
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.
Put the code coverage suppression comments around these.