-
Notifications
You must be signed in to change notification settings - Fork 603
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
add HasBlackBoxPath to BlackBoxUtils.scala #903
add HasBlackBoxPath to BlackBoxUtils.scala #903
Conversation
Can one of the admins verify this patch? |
ok to test |
LGTM, should we also changed |
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.
I think this looks fine. But I'd suggest if you have time that you add a bit of scala doc on
the add* methods.
@deprecated("Use addResource instead", "3.2") | ||
def setResource(blackBoxResource: String): Unit = addResource(blackBoxResource) | ||
|
||
def addResource(blackBoxResource: String): Unit = { |
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.
I think it would be nice to add some scaladoc here, in particular, providing an example
of what a resource path looks like.
trait HasBlackBoxPath extends BlackBox { | ||
self: BlackBox => | ||
|
||
def addPath(blackBoxPath: String): Unit = { |
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.
ScalaDoc here too. Probably worth mentioning that the working directory is
not likely to be the same as the target directory
…into HasBlackBoxPath
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.
LGTM
HasBlackBoxPath
that acts likeHasBlackBoxResource
except that it works with files outside of the resources directory.setResource
toaddResource
because multiple calls will result in multiple resources being copied to the target directory.Type of change: feature request
Impact: API addition (no impact on existing code)
Development Phase: implementation
Metadata: