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

[legacy] correctly pass boolean arguments in methods #130

Merged
merged 3 commits into from
Dec 17, 2018

Conversation

quezak
Copy link
Contributor

@quezak quezak commented Dec 17, 2018

Fixes #120

  • updated code generation for passing boolean arguments in methods
  • updated code generation for passing arrays, so nested boolean arguments work too
  • updated tests for the legacy target, to verify that boolean values are passed correctly

@coveralls
Copy link

coveralls commented Dec 17, 2018

Pull Request Test Coverage Report for Build 167

  • 5 of 5 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.09%) to 88.486%

Totals Coverage Status
Change from base Build 163: 0.09%
Covered Lines: 391
Relevant Lines: 426

💛 - Coveralls

scripts/test.sh Outdated
@@ -1,5 +1,6 @@
#!/usr/bin/env bash
set -e
set -x
cd "$(dirname "$0")"
Copy link
Member

Choose a reason for hiding this comment

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

are changes in this file really vital for this PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

not at all, I just found the test script output a bit unreadable -- I had some errors, but didn't know from which command or test file they originated

Copy link
Member

Choose a reason for hiding this comment

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

Can we just revert those? I use -x only for debugging purposes, I don't leave that in prod code (and this is how all other scripts are written).

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