Skip to content
This repository was archived by the owner on Jan 10, 2023. It is now read-only.

Update formatter to write to file #133

Merged
merged 8 commits into from
Jan 26, 2021
Merged

Update formatter to write to file #133

merged 8 commits into from
Jan 26, 2021

Conversation

thomasrockhu
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented Jan 25, 2021

Codecov Report

Merging #133 (112f398) into master (16f1af3) will not change coverage.
The diff coverage is 93.61%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #133   +/-   ##
=======================================
  Coverage   91.84%   91.84%           
=======================================
  Files           3        3           
  Lines         368      368           
=======================================
  Hits          338      338           
  Misses         30       30           
Impacted Files Coverage Δ
lib/codecov/formatter.rb 93.75% <93.47%> (ø)
lib/codecov.rb 100.00% <100.00%> (ø)

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 16f1af3...112f398. Read the comment docs.

@thomasrockhu thomasrockhu requested a review from a team January 25, 2021 23:27
@thomasrockhu thomasrockhu merged commit 9700fbe into master Jan 26, 2021
@thomasrockhu thomasrockhu deleted the 0.4.1 branch January 26, 2021 15:12
result_path = File.join(::SimpleCov.coverage_path, RESULT_FILE_NAME)
if File.writable?(result_path)
File.write(result_path, result['codecov'])
puts "Coverage report generated to #{result_path}.\#{result}"

Choose a reason for hiding this comment

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

@thomasrockhu Was it intended to leave the result in this logging statement? Printing the fairly large (depending on the number of tests) result adds significant clutter to the logged test output.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@davidrunger no not at all, apologies for the spam. I'll make a PR this week and release a new version that prints a shortened version (e.g. 4 ish lines?). Is that acceptable?

Choose a reason for hiding this comment

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

@thomasrockhu : No worries; not a big deal! :) Although personally I'd probably prefer that no lines be printed when it is successful, I can on the other hand certainly understand the possible benefits for debugging purposes, and printing 4ish lines also sounds fine to me. 👍Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@davidrunger, this has been updated in 0.4.3. Let me know if you run into issues!

Choose a reason for hiding this comment

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

Thank you, @thomasrockhu ! 🙇‍♂️ Version 0.4.3 works great. 👍

thomasrockhu referenced this pull request Feb 3, 2021
* Wrap file creation in try/catch

* Update CHANGELOG
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants