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.
binary
,gcov_args
,gcov_executable
,gcov_ignore
,gcov_include
,report_type
,skip_validation
, andswift_project
. Additionally, thefile
andplugin
arguments have been deprecated and replaced withfiles
andplugins
, respectively. These changes will ensure that the Action receives updates more quickly and provide developers with more flexibility in configuring their coverage reports. Furthermore, several existing arguments have been updated and improved, enhancing the overall functionality and usability of the Codecov GitHub Action.no_cheat.py
, which takes a generated diff file as an argument to accurately detect instances of linter disablement. The updated script then outputs the instances to a file calledcheats.txt
and fails the commit if more than one line is present, ensuring that instances of linter disablement are properly identified. This enhancement significantly improves the precision of the linter disablement check for pull requests and ensures that pylint disables are accurately tracked and reported, regardless of stacked pull requests.None
(#180). In this release, the behavior of skipping dataclass fields has been modified to allow skipping a field only when its value isNone
. This enhancement enables the writing of empty lists, strings, or zeros, addressing issue #179. The_marshal_dataclass
method, responsible for marshalling dataclasses, has been updated to replace the conditional statementif not raw:
withif raw is None:
. By checking for explicitNone
values, the new logic preserves empty lists, strings, or zeros and does not treat them asNone
, ensuring that these specific cases are not unnecessarily skipped. This change provides more control and precision when marshalling dataclasses in the open-source library.Dependency updates: