Setup QLTY for code coverage and linting #375
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces integration with Qlty Cloud for code coverage reporting, adds configuration files for Qlty, and makes several minor code and configuration improvements. The most significant changes are grouped below.
Qlty Cloud Integration:
qlty-action/coverageafter tests, using a secret token and the coverage result file..qlty/qlty.tomlconfiguration file and.qlty/.gitignoreto support Qlty CLI and Cloud, specifying exclude and test patterns, code smell thresholds, and source configuration. [1] [2]Configuration and Linting Improvements:
.rubocop.ymlto use the newpluginskey instead of the deprecatedrequirefor RuboCop extensions.Code Quality and Minor Fixes:
lib/ruby_units/unit.rbandlib/ruby_units/math.rbby simplifying conditionals and using more idiomatic Ruby syntax. [1] [2]lib/ruby_units/unit.rbfor better readability and maintainability. [1] [2] [3]RubyUnits::Unit.These changes collectively enhance test coverage visibility, code quality, and maintainability.