Skip to content
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

Accompanying change for s3mpi change to support safe = TRUE/FALSE #26

Merged
merged 4 commits into from
Feb 26, 2015

Conversation

kirillseva
Copy link
Collaborator

Bumped the package version so that we can later enforce it using the lockfile

# Since running syberia files is a reproducible process there
# shouldn't be a lot of damage done
# There is an option to overwrite this behavior
if (is.element('safe', names(opts))) args$safe <- opts$safe
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is the non-trailing-whitespace change

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not

args$safe <- opts$safe %||% args$safe

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to have the same style in two adjacent lines

if (is.element('safe', names(opts))) args$safe <- opts$safe
if (is.element('s3path', names(opts))) args$.path <- opts$s3path

Should I refactor both before merge?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes please, I don't know what I was thinking.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 0.0% when pulling b8505f6 on kirillseva:safe_store into 9c03797 on robertzk:master.

@@ -1,7 +1,7 @@
Package: syberiaStages
Type: Package
Title: Syberia Stages
Version: 0.2.1
Version: 0.3.0
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

0.2.2 please

@coveralls
Copy link

Coverage Status

Coverage remained the same at 0.0% when pulling bb9aff9 on kirillseva:safe_store into 9c03797 on robertzk:master.

@robertzk
Copy link
Owner

Looks good!

@coveralls
Copy link

Coverage Status

Coverage remained the same at 0.0% when pulling 93c457d on kirillseva:safe_store into 9c03797 on robertzk:master.

robertzk added a commit that referenced this pull request Feb 26, 2015
Accompanying change for s3mpi change to support safe = TRUE/FALSE
@robertzk robertzk merged commit 23f32ea into robertzk:master Feb 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants