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

Update specs to fix ruby 3 spec failures #174

Merged

Conversation

cthorn42
Copy link
Contributor

Ruby 3 changed the way positional and keyword arguments work. In order
to get specs to pass when we pass in a hash we need to use braces. This PR
addresses that.

Ruby 3 changed the way positional and keyword arguments work. In order
to get specs to pass when we pass in a hash we need to use braces. This PR
addresses that.
@codecov
Copy link

codecov bot commented Feb 17, 2022

Codecov Report

Merging #174 (22b5842) into master (3f94e94) will not change coverage.
The diff coverage is n/a.

❗ Current head 22b5842 differs from pull request most recent head 18ea959. Consider uploading reports for the commit 18ea959 to get more accurate results

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #174   +/-   ##
=======================================
  Coverage   78.07%   78.07%           
=======================================
  Files          15       15           
  Lines        1596     1596           
=======================================
  Hits         1246     1246           
  Misses        350      350           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3f94e94...18ea959. Read the comment docs.

@cthorn42
Copy link
Contributor Author

This will fix the failures we're seeing on #173.

@joshcooper joshcooper merged commit 21d055f into puppetlabs:master Feb 18, 2022
@cthorn42 cthorn42 changed the title (maint) Update specs to fix ruby 3 spec failures Update specs to fix ruby 3 spec failures Feb 22, 2022
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.

2 participants